Re-running changeset version and not appending to existing changelogs #1250
Unanswered
brad-mccormick
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We're about to go live with changesets and have a scenario:
Let's say we have some changesets, we run
changeset version
, but decided we need to release with a few more changes and new changesets are added. If I runchangeset version
again, it appends the changesets to the existing changelogs. This seems to make sense, but there could definitely be a case where we need to update the scope of the release without unnecessarily incremented package versions. How would we handle this workflow if we needed to?I have the github action in place, but not yet tested this scenario. The docs state:
Additionally the changeset docs state:
How does this PR get updated? The second doc states it's recreating the PR on merge. Will I run into the same problem where versions are being bumped for every change that's merged into the branch?
Beta Was this translation helpful? Give feedback.
All reactions