Version Packages (next)

.changeset/pre.json

@@ -9,6 +9,8 @@
     "chatty-kiwis-fold",
     "humble-weeks-watch",
     "lazy-jokes-camp",
+    "little-colts-bet",
+    "polite-carrots-exist",
     "six-eyes-return",
     "slick-bottles-try",
     "tidy-chefs-bake"

CHANGELOG.md

@@ -1,5 +1,17 @@
 # @changesets/ghcommit
 
+## 3.0.0-next.1
+
+### Minor Changes
+
+- [#116](https://github.com/changesets/ghcommit/pull/116) [`67853bf`](https://github.com/changesets/ghcommit/commit/67853bfb20c860ba1cb4069be443ba4e54c79095) Thanks [@bluwy](https://github.com/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](https://github.com/changesets/ghcommit/pull/111) [`1cf711e`](https://github.com/changesets/ghcommit/commit/1cf711eac92dc535787c3af3cc488989826ee43d) Thanks [@bluwy](https://github.com/bluwy)! - Support `branch` and `tag` format for `commitChangesFromRepo` `base` option. This aligns with the `commitFilesFromBase64` `base` option.
+
 ## 3.0.0-next.0
 
 ### Major Changes

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@changesets/ghcommit",
-  "version": "3.0.0-next.0",
+  "version": "3.0.0-next.1",
   "description": "Directly change files on github using the github API, to support GPG signing",
   "keywords": [
     "actions",