Skip to content

chore(release): one release at a time on this machine - #46

Merged
leemour merged 1 commit into
mainfrom
chore/release-lock
Oct 8, 2026
Merged

leemour merged 1 commit into
mainfrom
chore/release-lock

Conversation

@leemour

@leemour leemour commented Oct 8, 2026

Copy link
Copy Markdown
Owner

bin/release takes a machine-wide lock (`flock` on `$XDG_RUNTIME_DIR/leemour-release.lock`) before any npm or gh call and keeps it until the publish ends, so two sessions cannot release at once in any package. The release workflow gets a `concurrency` group.

Tested: the inserted lines refuse while the lock is held ("another release is running: …") and pass when free.

🤖 Generated with Claude Code

bin/release takes a machine-wide flock before any npm or gh call and holds
it until the publish finishes; a second release, in any of the packages,
is refused with who holds it. The release workflow gets a concurrency
group so two runs never publish at once.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@leemour
leemour merged commit caab5a6 into main Oct 8, 2026
4 checks passed
@leemour
leemour deleted the chore/release-lock branch October 8, 2026 21:44
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.

1 participant