Repository navigation
feat(plugins): add openspec - #7
Merged
Merged
Conversation
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.
Adds
plugins/openspec.tomlfor the OpenSpec CLI, using the standalone release binaries (no Node required).Verified
openspec-{linux,darwin}-{x64,arm64}.tar.gz,openspec-linux-{x64,arm64}-musl.tar.gz,openspec-windows-{x64,arm64}.zip, plus a sharedSHA256SUMS.vX.Y.Z, so URLs usev{version}.tofu.toml.exe-pathorarchive-prefix: the upstream installer extractsopenspecfrom the archive root, so the default exe name applies.Not verified
[install.libc] gnu = "": glibc assets have no suffix and musl assets use-musl. No other plugin in this catalog maps{libc}, and an empty value is untested. CI runs on ubuntu, so the smoke install exercises exactly this case. If it fails, drop[install.libc]and hardcodeopenspec-linux-{arch}.tar.gz(loses musl).Known limits
latestcan 404 for a few minutes after a new upstream tag, because the release is published before the binaries are attached. This can cause a flaky smoke test.