Add a sync guard for the vendored Allium plugin#12
Merged
yavorpanayotov merged 2 commits intoJun 19, 2026
Conversation
Allium is developed in juxt/allium and vendored here under plugins/allium so Codex (which only discovers local ./plugins/X marketplace entries) can install it. A vendored copy drifts from upstream silently — the existing remote-source entry was already several releases behind. Add scripts/sync-allium.sh, which vendors (or, with --check, verifies) plugins/allium against a juxt/allium ref pinned in scripts/allium-ref.txt, plus a CI workflow that fails when the two drift. To ship a new Allium release: bump allium-ref.txt, run the script, commit. Depends on juxt#11 (which introduces plugins/allium). Until that lands the check no-ops; the pinned ref matches the snapshot juxt#11 should vendor. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
yavorpanayotov
added a commit
to yenda/claude-plugins
that referenced
this pull request
Jun 19, 2026
Refresh the vendored snapshot to current juxt/allium main: picks up the lspServers block (juxt/allium#48), the external-API pattern (#46) and the zero-argument contract signature docs (#49). 229ccd0 also carries the .codex-plugin/plugin.json merged via #41, matching the ref pinned by the sync guard (juxt#12). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
yavorpanayotov
added a commit
that referenced
this pull request
Jun 19, 2026
* Expose Allium as local marketplace plugin * Re-vendor plugins/allium from juxt/allium@229ccd0 Refresh the vendored snapshot to current juxt/allium main: picks up the lspServers block (juxt/allium#48), the external-API pattern (#46) and the zero-argument contract signature docs (#49). 229ccd0 also carries the .codex-plugin/plugin.json merged via #41, matching the ref pinned by the sync guard (#12). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Yavor Panayotov <y.panayotov@yahoo.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jun 19, 2026
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
Adds tooling to keep the vendored
plugins/alliumfrom silently drifting out of date:scripts/sync-allium.sh— re-vendorsplugins/alliumfrom thejuxt/alliumref pinned inscripts/allium-ref.txt, or with--checkverifies the vendored copy matches that ref.scripts/allium-ref.txt— the pinned ref (currentlyjuxt/allium@229ccd0, i.e. the currentmain, which is ahead of thev3.3.0tag the marketplace previously pointed at)..github/workflows/check-allium-sync.yml— CI that runs--checkand fails on drift. Scoped to changes underplugins/allium/, the ref, or the tooling, so unrelated PRs are unaffected, and it no-ops untilplugins/alliumexists.Why
Allium is developed in
juxt/alliumand vendored here so Codex can install it (Codex only discovers local./plugins/Xmarketplace entries, not remotegithubsources — see #11). A vendored copy rots silently: the marketplace's previous remote entry was pinned tov3.3.0, already several merges behindmain(lspServers, the external-API pattern, zero-arg contract signatures). This makes the vendor reproducible and CI-enforced.To ship a new Allium release to the marketplace: bump
allium-ref.txt, runscripts/sync-allium.sh, commit.Depends on #11
#11 introduces
plugins/allium. Until it lands, the check no-ops. Bonus: #11's re-vendor can just bescripts/sync-allium.shfrom this PR instead of a manualrsync— and the pinned ref (229ccd0) is exactly the snapshot #11 should vendor, so once both land the check is green.Verified
(vendored output confirmed to include the Codex manifest and current
lspServers; not committed here — that's #11's job.)🤖 Generated with Claude Code