Skip to content

[v3-4-test] Describe where the dependency upgrade summary runs now (#76439) - #76454

Merged
potiuk merged 1 commit into
v3-4-testfrom
backport-629729a-v3-4-test
Nov 4, 2026
Merged

potiuk merged 1 commit into
v3-4-testfrom
backport-629729a-v3-4-test

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

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

…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
@potiuk
potiuk marked this pull request as ready for review November 4, 2026 14:57
@potiuk
potiuk enabled auto-merge (squash) November 4, 2026 14:57
@potiuk
potiuk merged commit c6cb20f into v3-4-test Nov 4, 2026
57 checks passed
@potiuk
potiuk deleted the backport-629729a-v3-4-test branch November 4, 2026 15:04
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant