Version Packages (next)#113
Open
changesets-org-version-bot[bot] wants to merge 1 commit into
Open
Conversation
aaa1f63 to
0befa98
Compare
0befa98 to
05c4b63
Compare
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.
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.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@changesets/ghcommit@3.0.0-next.1
Minor Changes
#116
67853bfThanks @bluwy! - Improve create, update, and force update handling incommitFilesFromBase64:baseis the same asbranchby comparing their SHAs instead of names.baseand branch HEAD SHAs match, instead of always a force update ifforceis true.refIdfromcommitFilesFromBase64(and consequentlycommitChangesFromRepo). If the commit fails, it'll throw an error instead, similar to existing parts of the implementation.#111
1cf711eThanks @bluwy! - Supportbranchandtagformat forcommitChangesFromRepobaseoption. This aligns with thecommitFilesFromBase64baseoption.