Repository navigation
core-is-not-public-on-homepage - #884
Merged
Merged
Conversation
VeryComplexAndLongName
force-pushed
the
core-is-not-public-on-homepage
branch
from
October 11, 2026 07:21
5d3aa5c to
d9007f7
Compare
VeryComplexAndLongName
force-pushed
the
core-is-not-public-on-homepage
branch
from
October 11, 2026 07:42
d9007f7 to
6012b07
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
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.
Mark Core non-public in the release manifest while retaining its stable internal record. Include visibility in the manifest fingerprint so CI publishes the metadata-only change without requiring a package version bump.
Verified locally: focused release-manifest tests (21/21), CLI typecheck and lint, strict OpenSpec validation. Production homepage confirmation remains after manifest synchronization.