Integrate changesets action to net-changesets

[magiino]

Use https://github.com/changesets/action in this repo for versioning and setup https://github.com/changesets/bot to check PRs.

[trueberryless]

This sounds very interesting.

I am just wondering how this will work. But I didn't look at all if the JS implementation is compatible with other languages as well, I guess it probably is.

Just one more thought: I personally always found it confusing in my Node projects, that the action is actually used for two things:

1. Creating PRs based on the changeset files that update versions and generate the CHANGELOG.md
2. Publishing the actual packages when no changeset files exists.

This just feels a little fragile to me, as I wouldn't expect that packages get published every time I have no changeset files, but I might miss some implementation details here. This might also be worth thinking about in a dedicated issue, but for now I thought it fits here as the decision whether to use the existing action or create a dedicated one is related.

---

Awesome project btw, I always wished there was a .NET port for changesets 🙌

[magiino]

I am just wondering how this will work. But I didn't look at all if the JS implementation is compatible with other languages as well, I guess it probably is.

JS implementation is not compatible with other languages, but there are workarounds for using it, which involve creating a package.json for every project and synchronizing it with .csproj. Which is too complicated. This .NET implementation removes all of that.

Here is a new documentation on how to integrate net-changesets with the original changesets action - https://github.com/solarwinds/net-changesets#changesets-github-action-integration-with-the-net-changesets-implementation

Just one more thought: I personally always found it confusing in my Node projects, that the action is actually used for two things:

Creating PRs based on the changeset files that update versions and generate the CHANGELOG.md
Publishing the actual packages when no changeset files exists.
This just feels a little fragile to me, as I wouldn't expect that packages get published every time I have no changeset files, but I might miss some implementation details here. This might also be worth thinking about in a dedicated issue, but for now I thought it fits here as the decision whether to use the existing action or create a dedicated one is related.

Hmm, I'm not aware of this - Publishing the actual packages when no changeset files exists.

The publish command is triggered only when you merge the generated PR created by the changesets GitHub action.

We do not plan to create a dedicated action; we can integrate the net-changeset with the existing changesets GH action. Documentation and demo are here - https://github.com/solarwinds/net-changesets#changesets-github-action-integration-with-the-net-changesets-implementation

If net-changesets would need something more from https://github.com/changesets/action, we can open a PR and change it.

[trueberryless]

Since the recent release of Changesets v3, the new action for it (v2) has actually addressed my concerns and split the logic into some sub-actions. A good example can be seen here.

And sorry that I wasn't aware that the net-changesets is compatible with the original changesets/action. This is super nice!

[magiino]

Oh, that is nice, I was not aware of the new changesets v3.

The original action is split into multiple actions and can still be used with the net-changesets implementation
by configuring the action with a custom input parameter called "script".

script = The command to use to version packages

Similarly to what was done in the old v2 action:

1. Install net-changesets tool
2. Supply custom script command for each action where you use net-changesets e.g.

I will try to create a new example for changesets v3 action integration with net-changesets soon.