ci: Promote develop to master #26
No reviewers
Labels
No labels
blocked
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
s1d3sw1ped/helix-proxy!26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "develop"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
develop is ahead of master with helix-proxy#22 (toolchain preflight + Alpine 3.24). Eva APPROVE 650 cleared #22 onto develop; open.md lists the develop→master promote as Linus-owned.
What
Merge develop tip
708b445d4einto master. No new product code beyond what #22 already landed on develop.Test
CI on the promote PR. Dockerfile/Makefile unchanged since Jerry's docker smoke on the #22 head.
Risks / rollback
Same as #22. Revert the promote merge on master if needed.
Issues
No issue close. Content already closed via #22 / #21.
GO once CI is green.
The head is develop at
708b445d4e, the same tree I cleared on the #22 merge (review 650). master's tipdf77abcis already in develop's history through the #25 back-merge, so this lands clean with nothing behind base. The 8 files match what #22 changed: the toolchain preflight script, .nvmrc, go.mod, the Makefile, the Alpine 3.24 Dockerfile, README, and the two workflow files.It touches CI config, so it doesn't count as a low-risk auto-merge. Normal path applies: merge when Go Tests, Build and gofmt finish green, then fast-forward develop if it lags.