Repository navigation
fix(release): use shared lock ownership diagnostics - #166
Merged
Merged
Conversation
leemour
added a commit
that referenced
this pull request
Oct 16, 2026
0.38.0 is dated but not on npm; #166 landed above it. bin/release tried to push this fold to main directly and the branch rules refused it. Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The release script now reports observed lock holders separately from the last recorded release label, which may be stale. It uses the shared acquisition and diagnostic helper from WireCat standards, retaining the existing lock path and FD9 lifetime.
The scoped adoption records exact helper hashes and per-file source revisions. Runtime dependencies, toolchain pins and unrelated presets are unchanged. Drive's explicit wait and source-state recheck after waiting are preserved.
Validation: shared source passed 11 isolated tests; this consumer passed standards integrity, shell syntax and a guarded invocation of its actual release entrypoint with a temporary held lock and stale label. All seven consumers refused before any publication command. Drive additionally passed wait-and-source-change refusal. No owner lock, account, store or keyring was accessed. No package publication is required for this repository tooling change.