Restore patch-rebuild.yml workflow gutted during PR-build development#35
Merged
Conversation
The workflow was replaced with an 11-line dev stub in 1cf855f that invoked pr-build.yml@feat/sideloader with a hardcoded pr_number: '31' — a leftover from PR-build-flow development that didn't belong on master. Restore the original two-job workflow: `prepare` reads upstream/ {quality}.json, computes a time-based RELEASE_VERSION, and commits PATCH_REBUILD_INFO.md for traceability; `trigger-all-builds` fires repository_dispatch: [{quality}] with patch_rebuild + custom version so check_tags.sh forces SHOULD_BUILD=yes, SHOULD_DEPLOY=yes regardless of the normal upstream-version gate. This is the forcing function for releases when nothing in upstream/ stable.json changed — e.g. shipping a Codex patch fix, a bundled- extension bump, or branding tweaks. Content restored from 1cf855f~1 verbatim; downstream plumbing (PATCH_REBUILD, CUSTOM_RELEASE_VERSION, GITHUB_EVENT_CLIENT_PAYLOAD) in stable-{linux,macos,windows}.yml is already in place.
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
2 participants
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.
Restores
.github/workflows/patch-rebuild.ymlto its pre-1cf855f form. The workflow was replaced with a dev-time stub targetingpr-build.yml@feat/sideloaderwith a hardcoded PR number — it can't produce a stable release in that state.Changes
.github/workflows/patch-rebuild.yml— restored byte-identically from1cf855f~1. Two jobs:prepare(compute time-based RELEASE_VERSION, commitPATCH_REBUILD_INFO.md) andtrigger-all-builds(repository_dispatch: [${quality}]withpatch_rebuild: trueandcustom_release_version).No other files touched — the downstream
PATCH_REBUILD/CUSTOM_RELEASE_VERSIONplumbing instable-{linux,macos,windows}.ymlis still in place and was not affected by the 48h of CI changes.Test plan
git diff 1cf855f~1 -- .github/workflows/patch-rebuild.ymlis empty (confirmed locally).quality(stable/insider) +reasoninputs restored.quality=stable,reason="verify restore"to confirm the marker commit lands on master and the threestable-*workflows are triggered via repository_dispatch. Only do this if a real forced rebuild is desired; it will produce a live release.