@exadev/semantic-release-workspace 1.2.2 → 1.2.4

package/dist/cli.js

@@ -14,7 +14,7 @@ import { glob } from "tinyglobby";
 import { parse } from "yaml";
 import { pathToFileURL } from "node:url";
 //#region package.json
-var version = "1.2.2";
+var version = "1.2.4";
 //#endregion
 //#region src/errors.ts
 /**
@@ -299,10 +299,11 @@ async function assertCleanWorkingTree(options) {
 	const changes = await workingTreeChanges(options);
 	if (changes.length > 0) throw new WorkspaceStateError(`The working tree in ${options.cwd} is not clean: ${changes.join(", ")}. commitStrategy "single" discovers what it touched via "git status", so it requires a clean tree to start from; commit, stash elsewhere, or discard these changes first.`);
 }
-/** Pushes the current branch's head and a set of tags to origin in one push, so a combined release commit and every tag pointing at it land on the remote as a single atomic-looking update rather than as separate pushes an interrupted run could split across. */
+/** Pushes the current branch's head and a set of tags to origin as one atomic update: either every ref lands or none do. `--atomic` is load-bearing, not cosmetic -- a plain multi-refspec `git push` negotiates each ref independently, so a branch update the remote rejects (e.g. a non-fast-forward, because an ordinary PR merged to this branch while this run was still preparing its own commit) can still let the tag refs through, since a brand-new tag has no fast-forward constraint to fail. That leaves a tag on the remote with no commit reachable from the branch behind it -- and because the release this tag names gets recomputed identically, deterministically, from the branch's own commit history on every future run, a stranded tag is not a one-off failure: it is a permanent block, since `git tag <name>` refuses to recreate a name that already exists. Atomicity turns a silent partial success into a clean, retriable failure: the branch and its tags either both advance together, or neither does, so a rejected push leaves nothing behind for the next run to trip over. */
 async function pushHeadAndTags(tagNames, options) {
 	await git([
 		"push",
+		"--atomic",
 		"origin",
 		`HEAD:${await currentBranch(options)}`,
 		...tagNames

package/dist/index.cjs

@@ -250,10 +250,11 @@ async function assertCleanWorkingTree(options) {
 	const changes = await workingTreeChanges(options);
 	if (changes.length > 0) throw new WorkspaceStateError(`The working tree in ${options.cwd} is not clean: ${changes.join(", ")}. commitStrategy "single" discovers what it touched via "git status", so it requires a clean tree to start from; commit, stash elsewhere, or discard these changes first.`);
 }
-/** Pushes the current branch's head and a set of tags to origin in one push, so a combined release commit and every tag pointing at it land on the remote as a single atomic-looking update rather than as separate pushes an interrupted run could split across. */
+/** Pushes the current branch's head and a set of tags to origin as one atomic update: either every ref lands or none do. `--atomic` is load-bearing, not cosmetic -- a plain multi-refspec `git push` negotiates each ref independently, so a branch update the remote rejects (e.g. a non-fast-forward, because an ordinary PR merged to this branch while this run was still preparing its own commit) can still let the tag refs through, since a brand-new tag has no fast-forward constraint to fail. That leaves a tag on the remote with no commit reachable from the branch behind it -- and because the release this tag names gets recomputed identically, deterministically, from the branch's own commit history on every future run, a stranded tag is not a one-off failure: it is a permanent block, since `git tag <name>` refuses to recreate a name that already exists. Atomicity turns a silent partial success into a clean, retriable failure: the branch and its tags either both advance together, or neither does, so a rejected push leaves nothing behind for the next run to trip over. */
 async function pushHeadAndTags(tagNames, options) {
 	await git([
 		"push",
+		"--atomic",
 		"origin",
 		`HEAD:${await currentBranch(options)}`,
 		...tagNames

package/dist/index.js

@@ -225,10 +225,11 @@ async function assertCleanWorkingTree(options) {
 	const changes = await workingTreeChanges(options);
 	if (changes.length > 0) throw new WorkspaceStateError(`The working tree in ${options.cwd} is not clean: ${changes.join(", ")}. commitStrategy "single" discovers what it touched via "git status", so it requires a clean tree to start from; commit, stash elsewhere, or discard these changes first.`);
 }
-/** Pushes the current branch's head and a set of tags to origin in one push, so a combined release commit and every tag pointing at it land on the remote as a single atomic-looking update rather than as separate pushes an interrupted run could split across. */
+/** Pushes the current branch's head and a set of tags to origin as one atomic update: either every ref lands or none do. `--atomic` is load-bearing, not cosmetic -- a plain multi-refspec `git push` negotiates each ref independently, so a branch update the remote rejects (e.g. a non-fast-forward, because an ordinary PR merged to this branch while this run was still preparing its own commit) can still let the tag refs through, since a brand-new tag has no fast-forward constraint to fail. That leaves a tag on the remote with no commit reachable from the branch behind it -- and because the release this tag names gets recomputed identically, deterministically, from the branch's own commit history on every future run, a stranded tag is not a one-off failure: it is a permanent block, since `git tag <name>` refuses to recreate a name that already exists. Atomicity turns a silent partial success into a clean, retriable failure: the branch and its tags either both advance together, or neither does, so a rejected push leaves nothing behind for the next run to trip over. */
 async function pushHeadAndTags(tagNames, options) {
 	await git([
 		"push",
+		"--atomic",
 		"origin",
 		`HEAD:${await currentBranch(options)}`,
 		...tagNames

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@exadev/semantic-release-workspace",
-  "version": "1.2.2",
+  "version": "1.2.4",
   "description": "Independent per-package semantic-release orchestration for pnpm workspaces, without lockstep versioning.",
   "type": "module",
   "repository": {