Skip to content

Back-merge main into develop after v1.18.1 - #962

Merged
VijitSingh97 merged 5 commits into
developfrom
main
Aug 14, 2026
Merged

Back-merge main into develop after v1.18.1#962
VijitSingh97 merged 5 commits into
developfrom
main

Conversation

@VijitSingh97

Copy link
Copy Markdown
Collaborator

Post-release back-merge per the branch model: the v1.18.0/v1.18.1 prep commits, the committed cosign.pub (#961), and both release merge commits return to develop, keeping main an ancestor of develop for the next cut.

🤖 Generated with Claude Code

VijitSingh97 and others added 5 commits August 13, 2026 23:32
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
release: v1.18.1 — supersede the unsigned 1.18.0 bundle
…bootstrap)

The key pair was generated on the release box in July but the public half never
landed in the repo, so release.sh's signing condition (key + committed cosign.pub)
has never fired and every bundle to date shipped unsigned. Committing the pub key
completes the #376 rollout: the pipeline signs from the next cut, the bundle ships
the key, and installs bootstrap verification on their first upgrade to it. Also
corrects the 1.18.1 changelog account to this real story.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
release: commit cosign.pub — signing engages for the first time (#376 bootstrap)
@VijitSingh97
VijitSingh97 merged commit 0be84e7 into develop Aug 14, 2026
32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant