dsanders11

#52035: ci: calculate rerun apply patches date from first run attempt

Merged
Created: Jun 17, 2026, 3:30:43 AM
Merged: Jun 18, 2026, 2:09:37 PM
10 comments
Target: main

Description of Change

Follow-up to #51524, which didn't fully fix the issue as it was pulling the age of the most recent run, while GitHub uses the age of the first run.

It looks like there was also a Trop hiccup on #51524 and it didn't get backported to all of the target branches, so when I backport this PR I'll roll those changes into the branches that didn't get that PR originally.

Checklist

  • I have built and tested this change
  • I have filled out the PR description

Release Notes

Notes: none

Backports

40-x-y
In-flight
PR Number
#52073
Waiting to be merged
41-x-y
In-flight
PR Number
#52077
Waiting to be merged
42-x-y
In-flight
PR Number
#52076
Waiting to be merged
43-x-y
In-flight
PR Number
#52075
Waiting to be merged

Semver Impact

Major
Breaking changes
Minor
New features
Patch
Bug fixes
None
Docs, tests, etc.

Semantic Versioning helps users understand the impact of updates:

  • Major (X.y.z): Breaking changes that may require code modifications
  • Minor (x.Y.z): New features that maintain backward compatibility
  • Patch (x.y.Z): Bug fixes that don't change the API
  • None: Changes that don't affect using facing parts of Electron