Version Packages

[changesets-org-version-bot]

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

@changesets/ghcommit@3.0.0

Major Changes

• #91 9ac746d Thanks @bluwy! - Remove queries export from index. You should not rely on these queries as stable APIs.

• #89 e34689e Thanks @bluwy! - Add "engines" field for explicit node version support. The supported node versions are ^22.11 || ^24 || >=26.

• #109 203f0b7 Thanks @bluwy! - Removed the commitFilesFromBuffers and commitFilesFromDirectory APIs. These APIs were simple wrappers over the core commitChangesFromBase64 API, which should be used instead. Read the file and pass the base64-encoded content to commitChangesFromBase64 fileChanges directly. For example:

  • Buffer.from("hello world").toString("base64")
  • await fs.readFile("path/to/file", "base64")

• #118 e2b975d Thanks @bluwy! - Remove recursivelyFindRoot and make cwd optional for commitChangesSinceBase. Files will also not be filtered by cwd by default. To only commit files from a directory, use the filterFiles option instead.

• #88 19ea73a Thanks @bluwy! - Publish code as ESM only

• #109 203f0b7 Thanks @bluwy! - Removed all subpath exports. All APIs should be imported from root, e.g. import { commitChangesFromRepo } from "@changesets/ghcommit".

• #117 165c6cb Thanks @bluwy! - Rename public APIs and export types. Note that the existing changelog may still reference the old names, but the new names should be used instead.

  • commitFilesFromBase64 -> commitChanges
  • commitChangesFromRepo -> commitChangesSinceBase

• #110 ead1e55 Thanks @bluwy! - Remove log argument from APIs. If you need to debug the package, use breakpoints or manually add logs in the package code.

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.

• #108 8b5585d Thanks @bluwy! - Replace isomorphic-git with direct git command calls to get the file changes since a given ref