Vendor allium v3.4.0 (pin to release tag)#13
Merged
Conversation
Re-vendor plugins/allium from the juxt/allium v3.4.0 release tag (was pinned to a raw main SHA). Picks up the plugin 3.4.0 version bump in both manifests. Pinning to a tag instead of a SHA makes the vendored copy traceable to a release. Co-Authored-By: Claude Opus 4.8 (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.
What
Re-vendors
plugins/alliumfrom thejuxt/alliumv3.4.0 release tag and updatesscripts/allium-ref.txtaccordingly (was a rawmainSHA).Why
Verified
Vendored manifests now report version 3.4.0.
🤖 Generated with Claude Code