Repository navigation
[v3-4-test] Describe where the dependency upgrade summary runs now (#76439) - #76454
Merged
Merged
Conversation
…76439) Since #76251 the CI docs sent readers to the wrong workflow and claimed that canaries with failed jobs save no report inputs. Those canaries now get a report, with its explanation jobs, so anyone estimating report runs or their cost from the docs would come out too low. The docs also still credited basic tests with upgrade monitoring, which left since #64836, so a reader looking for this check got two answers. (cherry picked from commit 629729a) Co-authored-by: Jarek Potiuk <jarek@potiuk.com> Generated-by: Claude Opus 5
1 task done
potiuk
marked this pull request as ready for review
November 4, 2026 14:57
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
choo121600,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl,
potiuk and
vatsrahul1001
as code owners
November 4, 2026 14:57
potiuk
enabled auto-merge (squash)
November 4, 2026 14:57
vatsrahul1001
pushed a commit
that referenced
this pull request
Nov 4, 2026
…76439) (#76454) Since #76251 the CI docs sent readers to the wrong workflow and claimed that canaries with failed jobs save no report inputs. Those canaries now get a report, with its explanation jobs, so anyone estimating report runs or their cost from the docs would come out too low. The docs also still credited basic tests with upgrade monitoring, which left since #64836, so a reader looking for this check got two answers. (cherry picked from commit 629729a) Generated-by: Claude Opus 5 Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Nov 4, 2026
…76439) (#76454) Since #76251 the CI docs sent readers to the wrong workflow and claimed that canaries with failed jobs save no report inputs. Those canaries now get a report, with its explanation jobs, so anyone estimating report runs or their cost from the docs would come out too low. The docs also still credited basic tests with upgrade monitoring, which left since #64836, so a reader looking for this check got two answers. (cherry picked from commit 629729a) Generated-by: Claude Opus 5 Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Nov 4, 2026
…76439) (#76454) Since #76251 the CI docs sent readers to the wrong workflow and claimed that canaries with failed jobs save no report inputs. Those canaries now get a report, with its explanation jobs, so anyone estimating report runs or their cost from the docs would come out too low. The docs also still credited basic tests with upgrade monitoring, which left since #64836, so a reader looking for this check got two answers. (cherry picked from commit 629729a) Generated-by: Claude Opus 5 Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Nov 5, 2026
…76439) (#76454) Since #76251 the CI docs sent readers to the wrong workflow and claimed that canaries with failed jobs save no report inputs. Those canaries now get a report, with its explanation jobs, so anyone estimating report runs or their cost from the docs would come out too low. The docs also still credited basic tests with upgrade monitoring, which left since #64836, so a reader looking for this check got two answers. (cherry picked from commit 629729a) Generated-by: Claude Opus 5 Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Nov 5, 2026
…76439) (#76454) Since #76251 the CI docs sent readers to the wrong workflow and claimed that canaries with failed jobs save no report inputs. Those canaries now get a report, with its explanation jobs, so anyone estimating report runs or their cost from the docs would come out too low. The docs also still credited basic tests with upgrade monitoring, which left since #64836, so a reader looking for this check got two answers. (cherry picked from commit 629729a) Generated-by: Claude Opus 5 Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
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.
Since #76251 the CI docs sent readers to the wrong workflow and claimed that canaries with failed
jobs save no report inputs. Those canaries now get a report, with its explanation jobs, so anyone
estimating report runs or their cost from the docs would come out too low. The docs also still
credited basic tests with upgrade monitoring, which left since #64836, so a reader looking for
this check got two answers.
(cherry picked from commit 629729a)
Co-authored-by: Jarek Potiuk jarek@potiuk.com
Generated-by: Claude Opus 5