Repository navigation
chore(release): release data for v1.2.13 - #438
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.
Written by the release workflow from the bytes published on v1.2.13: sha256 and release_signature per plugin. Review the diff against the Release assets; do not edit by hand.
Before merging: registry.json, catalog.json and counts.json are projections of releases.json that need the private bundles repo, which the workflow token cannot read.
Run bash scripts/plugin-counts.sh on a maintainer machine with the bundles checkout and push the result to this branch; the registry gate stays red until then.
Pushing also starts the required checks, which a PR opened with the workflow token does not.