Skip to content

Version Packages (next)#113

Open
changesets-org-version-bot[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

Version Packages (next)#113
changesets-org-version-bot[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@changesets-org-version-bot

@changesets-org-version-bot changesets-org-version-bot Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

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.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@changesets/ghcommit@3.0.0-next.1

Minor Changes

  • #116 67853bf Thanks @bluwy! - Improve create, update, and force update handling in commitFilesFromBase64:

    • Correctly detect if the base is the same as branch by comparing their SHAs instead of names.
    • Perform a normal update if the branch exists and the base and branch HEAD SHAs match, instead of always a force update if force is true.
    • Always clean up created or existing temporary branches during force updates, even if it fails.
    • Always return a non-nullable refId from commitFilesFromBase64 (and consequently commitChangesFromRepo). If the commit fails, it'll throw an error instead, similar to existing parts of the implementation.
  • #111 1cf711e Thanks @bluwy! - Support branch and tag format for commitChangesFromRepo base option. This aligns with the commitFilesFromBase64 base option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants