docs(release): v1.6.0 notes - #61
Open
pedromvgomes wants to merge 1 commit into
Open
Conversation
Covers pipeline.{ci,cd}.independent_stages (#60): why a fixed graph is
still right, why an edge is a claim a repository can be right to deny,
and the measured eleven minutes wardnet would otherwise pay per daemon
PR waiting on artefacts its e2e suite never reads.
Two sections carry the load. "What it deliberately cannot do" states the
constraint that keeps the graph fixed — a named stage removes a sibling
edge, never adds or reorders one. "Detaching a stage does not ungate it"
says outright that ci-gate still waits on the stage, because a speed
change that quietly weakened branch protection is the worst way this
could be misread.
Upgrading is the inverse of v1.5.0: nothing to do, no fleet sync, no
re-render, verified by a byte-identical render diff against v1.5.0.
|
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.
Release notes for v1.6.0, covering
pipeline.{ci,cd}.independent_stages(#60).Same convention as v1.5.0: the notes commit is the tagged commit, so merging this is what v1.6.0 gets cut from, then
v1moves.What the notes cover
builduploads; serialising them takes a daemon PR from ~24m to ~35m. From run 32688637246, not estimated.Two sections carrying the weight
## Detaching a stage does not ungate itsays outright thatci-gatestill waits on the stage and a failing end2end still blocks the merge. That's the one way this feature could be badly misread, and a speed change that quietly weakened branch protection would be the worst outcome available — so it's stated plainly rather than left implicit.## Upgradingis the inverse of v1.5.0: nothing to do, no fleet sync, no re-render. Verified by a byte-identical render diff against v1.5.0 (bc668c9), comments included. Worth the contrast being explicit, since the previous release did want a fleet sync.It also closes with the one caution I'd want a reader to take away: adopt it only where the claim is actually true, because the default edge costs time but never correctness, and being wrong here means testing a build you didn't wait for.
Range
v1.5.0..mainis exactly one commit (#60), so there's nothing else to fold in.