chore: version packages - #367
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 11, 2026 18:36
1a943f2 to
090d886
Compare
Contributor
Author
🔒 Security scan
Details: Security tab · workflow run. |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 11, 2026 20:16
090d886 to
b4afc16
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@pacto/core@3.3.1
Patch Changes
36e2ef2: Stop the OCI bundle cache from reporting a failure when a concurrent pull of the
same reference commits first.
A cache entry is built in a staging directory and swapped into place with one
rename, so a reader sees a whole entry or none. Two pulls of the same reference
aim at the same destination, though, and nothing serializes them — the second
pull is usually a second
pactoprocess sharing one cache directory. Both clearthe destination, one rename lands, and the loser's fails onto the winner's fresh
entry with
directory not empty.Nothing was wrong: the entry the losing pull set out to write was on disk, put
there whole by the other one. But the loser reported the rename error, and the
caller logs it, so a healthy parallel pull told the user
could not cache the pulled bundle. The commit now asks the filesystem what is actually there andtreats a lost race as the success it was.
@pacto/dashboard-contract-bundle@3.3.1
@pacto/demo-bundles@3.3.1
@pacto/demo-compose@3.3.1
@pacto/cli@3.3.1
@pacto/dashboard-image@3.3.1