CI: trigger frontend build on pushes to N.x version branches#3873
Merged
Conversation
The pipeline already runs on pushes to N.N version branches (2025.4, 2026.2, ...) and rebuilds/repackages the frontend, which incidentally sweeps any stray build-dist/build-*.zip via package-build.cjs. This means the two-zip state that can result from a bad merge self-heals on the next push to those branches. The 2026.x development branch is not covered by the current [0-9]+.[0-9]+ glob, so a merge that lands two archives on 2026.x is not repaired until someone changes assets/**. Add [0-9]+.x to close that gap. No new logic, no guard step - the existing pipeline is the guard.
|
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Add
[0-9]+.xtopush.branchesin .github/workflows/frontend-build-pr.yaml so2026.xruns the frontend build on every push — same as2025.4and2026.2already do.The pipeline rebuilds and repackages on every push, and
package-build.cjssweeps any straybuild-dist/build-*.zipas a side effect. That makes the "two archives after a bad merge" state self-heal. Today it only self-heals on[0-9]+.[0-9]+branches; this extends it to[0-9]+.x.