Repository navigation
cli-is-visible-on-the-homepage - #878
Merged
Merged
Conversation
Merged
VeryComplexAndLongName
marked this pull request as ready for review
October 10, 2026 20:14
VeryComplexAndLongName
enabled auto-merge (squash)
October 10, 2026 20:20
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.
Expose the stable ci-cli product as public in schema-1 release manifests, with its npm package link, summary and existing version/notes. Include a minor CLI changeset to trigger normal manifest publication after versioning.
Homepage consumers have merged as OpenSpec-UI-Homepage #139 and #140. Local targeted manifest tests passed (20), workspace typecheck/lint passed. Full Windows gate encountered Git Bash failure and a dynamic-import timeout; WSL dependency install hit DNS EAI_AGAIN. Keep draft until Linux CI and exact-command contract verification are recorded, then rerun the open-item gate.
Post-merge production proof is separately tracked in the owner-approved cli-homepage-rollout change. No new GitHub CLI release or npm publish is performed.