Repository navigation
release: the seal and the publication follow the release they seal - #933
Merged
Merged
Conversation
Sunrisepeak
force-pushed
the
fix/2026.11.13.1-release-seal
branch
from
November 14, 2026 12:15
9b7ae58 to
222f43a
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
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 run of v2026.11.13.1 (43590596177) created the release and skipped
release-manifestandpublish-ecosystem. A job without a condition runs only when every job before it, transitively, succeeded; the canaries job, skipped in a release started withoutcanaries, skipped both.Each job now states the one job it follows:
release-manifestruns whencreate-releasesucceeded, andpublish-ecosystemwhenrelease-manifestsucceeded. The release of v2026.11.13.1 is completed by a dispatch withtag: v2026.11.13.1, which rebuilds that tag's commit.