Repository navigation
docs(release): the first package took the repository's visibility - #9
Merged
Merged
Conversation
v0.1.0's image was public from its first push, since the organisation allows public packages and the package is linked to the public repository; the checklist now says so, and keeps the manual step for a package that comes out private.
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.
The release checklist expected GHCR to create the first package private, so that verify would fail until someone made it public. For v0.1.0 it did not: with public packages allowed in the organisation, the package linked to this public repository was public from its first push, and both verify jobs passed on the first run. The checklist now says so and keeps the manual step for a package that comes out private.