[wp-trac] [WordPress Trac] #64083: Trim the GitHub Actions workflows for older branches (and possibly `trunk`)

[WordPress Trac]

#64083: Trim the GitHub Actions workflows for older branches (and possibly `trunk`)
------------------------------+--------------------------
 Reporter:  johnbillion       |       Owner:  johnbillion
     Type:  task (blessed)    |      Status:  reopened
 Priority:  normal            |   Milestone:  7.0
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch         |     Focuses:
------------------------------+--------------------------
Changes (by desrosj):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 @johnbillion reopening this because it seems like the commit to the `6.0`
 branch caused some
 [https://github.com/WordPress/WordPress/commit/689efdf08705d2f352a70f633dd6e0c7906b0355
 unexpected changes to the built files].

 I noticed the `6.0-branch` branch as one of two in the Active list by
 chance looking into whether the branch created in [61863] made it to the
 WordPress/WordPress mirror on GitHub.

 I'm not at all clear what caused this since no changes were made to
 `package.json` or `package-lock.json`, but a good number of JavaScript
 files and any generated files containing computed hashes of those files
 were updated. The changes all seem similar to what you'd expect if
 `webpack` or a related dependency were updated, and I believe the changes
 all look OK.

 But this will increase the package size for the next 6.0 auto-update
 should a security patch need to be shipped to this branch.

 I'm reopening for now just to look into this a bit more. It would be good
 to understand what happened.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64083#comment:61>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform