Meta changes

Problem

Sometimes changes won’t end up in the final artifact but rather will impact the product in some other way.

For example:

• improving CI setup,
• improving docs,

Let’s call these meta changes.

I am pretty new to changesets but I think there is no way to express such changes in the changelog, yet I think it’s often valuable to note them.

Proposed solution

Introduce new change type - meta, next to patch/minor/major. This wouldn’t bump package version in any way but would endup in the changelog.

[Andarist]

You can use none type but I’m not sure if those get printed in changelog files. I would have to re-check it later.

[Andarist]

There were some similar requests (but not the same in the past) - we’d like to cover more workflows but we need to first observe such feature requests to be able to design a proper solution.

I hope you will enjoy Changesets after working with them a little bit more (I highly recommend setting up both our bot and our GitHub action). I’m certainly very happy with this project - note that I’m just a user who tries to help out here, not the original author of Changesets, so it’s not like I’m trying to advertise my own project, I’m just spreading the love for what I have found to be very useful.

It’s also interesting that both Yarn 2 and Rush.js have developed, independently, somewhat similar solutions for this exact problem - so I would say that we are onto something here 😉