Record published version 0.5.12 - #278
Open
gh-contract-review[bot] wants to merge 1 commit into
Open
gh-contract-review[bot] wants to merge 1 commit into
gh-contract-review[bot] wants to merge 1 commit into
Conversation
Prepared automatically after publishing v0.5.12. Publish run: 35862744706
gh-contract-review
Bot
force-pushed
the
chore/record-published-version
branch
from
September 23, 2026 12:51
e43bb86 to
34076dd
Compare
gh-contract-review
Bot
changed the title
This branch has not been deployed
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
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.
0.5.12is published;mainrecords0.5.10.The tag is the source of truth for what gets published. This brings the repository's own
copy in line, so that a git installation, an SBOM built from a checkout,
npm packandpatchstack-connect --versionall report the released version.Prepared by the
Publishworkflow. Two version strings and the lockfile entriesnpm versionderives from them; no source changes.Version consistency check: success (run inside the workflow).
Published tarball verification: failure.
The published tarball did NOT pass its canary.
0.5.12is on npm and cannot beunpublished — decide whether to deprecate it before treating this pull request as
routine. It is opened regardless, because a repository naming a version other than the
one that was released is a second problem rather than a safeguard against the first.
The proposal App opened this pull request so its required CI checks run normally.
It can merge automatically only after those checks and the publishing run pass.