`getChangelogEntry` should use `readChangesetState` install of reading `changelog` file?

[JounQin]

At stylelint/stylelint#6299, we're using our own format of CHANGELOG without major/minor/patch sections. It results stylelint/stylelint#6301

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

I think readChangesetState can/should handle this case, because they have the meta information without generated CHANGELOG.

[bluwy]

I don't think we can address this until we can fix it in core first. We should track this in these issues:

• Document initial CHANGELOG.md format requirements changesets#959
• Introduce ComVer - Compatibility Versioning changesets#1241
• Support custom update types in changeset files changesets#1497