Masafumi Koba

@JounQin @hudochenkov Thanks for clearing the details! It seems good to start at a minimum to evaluate the new workflow: - Install https://github.com/apps/changeset-bot - Add https://github.com/changesets/action We can update `CHANGELOG.md`...

@jeddy3 Thanks for the feedback. First, I'll try only the changelog automation. Then, if it doesn't fit, let's revert it. @JounQin I've installed [changeset-bot](https://github.com/apps/changeset-bot). Could you please open a pull...

Since there are some problems found in PR #6282, let's try the new workflow in the next iteration (after [14.11.0](https://github.com/stylelint/stylelint/issues/6280))!

[14.12.0](https://github.com/stylelint/stylelint/releases/tag/14.12.0) is the first version using the changelog generation! We evaluate that it is easier to update the changelog than before. But, we encounter a small problem with GitHub Releases....

It seems we can now evaluate the new changelog automation workflow. What do you think? If no objections, we should update the following parts in the maintainer guide: https://github.com/stylelint/stylelint/blob/e3421aa7d9465f2f5272191d2036b0fd44d14145/docs/maintainer-guide/pull-requests.md?plain=1#L27-L32 https://github.com/stylelint/stylelint/blob/e3421aa7d9465f2f5272191d2036b0fd44d14145/docs/maintainer-guide/releases.md?plain=1#L8-L12

@JounQin Please let me ask a few questions. 1. If we publish on CI, will the following 3 to 5 steps no longer be needed? https://github.com/stylelint/stylelint/blob/eee9deb35190f46c5f964769d521fef5d7d1d7a8/docs/maintainer-guide/releases.md?plain=1#L13-L15 2. Will changes for...

@JounQin Thanks for the answer. > generate GitHub release (But the release content could be different with our format) Regarding this, it seems possible to prevent generating a GitHub release...

> I'm not sure to understand this part, if the CI job fails, we can just retry it and when the npm version is not published, `changesets` will still recognize...

@JounQin Thanks for the explanation. I understand well. 👍🏼 I'd like to hear @jeddy3's idea.

> * during a release, we're in the terminal anyway to perform other updates (e.g., to the website and demo) That makes sense. I have no objections. 👍🏼