chore(publish): Bump next entries in changelog when releasing#290
Open
chore(publish): Bump next entries in changelog when releasing#290
next entries in changelog when releasing#290Conversation
Semver Impact of This PR🟢 Patch (bug fixes) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨Attributes
Other
Bug Fixes 🐛
Documentation 📚
Internal Changes 🔧Deps
Deps Dev
Other
🤖 This preview updates automatically when you update the PR. |
next entries in changelog when releasingnext entries in changelog when releasing
ericapisani
approved these changes
Mar 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We recently added changelog entries to the attribute schema and decided to tag yet unreleased changes with
"next". This PR now ensures that allnextentries are changed to the version to be released via our craft pre-release script. Importantly, this means we also need to regenerate the JS and python code after bumping since the changelog is added to the generated code metadata.This script also does some cleanup like merging PRs mentioned multiple times. Tested locally and ensured it's idempotent. This should be good enough for releasing.