Skip to content

release: staging to main, 2026-10-06 - #49

Open
bryanfawcett wants to merge 1 commit into
mainfrom
release/staging-to-main-2026-10-06
Open

bryanfawcett wants to merge 1 commit into
mainfrom
release/staging-to-main-2026-10-06

Conversation

@bryanfawcett

Copy link
Copy Markdown
Collaborator

Release of staging to main. The branch is built from main with staging's exact tree (git diff origin/staging is empty; tree SHAs match).

What ships

  • ci.yml: CI also runs on pushes to staging.

main was 1 commit ahead of staging (#46, release versioning policy). Its content is already in staging via #47 — git diff origin/main origin/staging touches only ci.yml — so nothing on main is dropped.

On main, release.yml runs and finds version 0.2.0-beta.1 already released, so it publishes nothing (same as the last runs on main). Workflows validated with actionlint (clean).

🤖 Generated with Claude Code

https://claude.ai/code/session_01GHjaH1Vt2dVLWU68iz8tFq

Builds main's next state from staging's exact tree.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GHjaH1Vt2dVLWU68iz8tFq
Signed-off-by: Bryan Fawcett <bryan@nyuchi.com>

This branch has not been deployed

No deployments
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