Skip to content

chore: sync main into beta - #52

Closed
github-actions[bot] wants to merge 3 commits into
betafrom
main
Closed

chore: sync main into beta#52
github-actions[bot] wants to merge 3 commits into
betafrom
main

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Synchronizes main into beta. Merge this PR after CI passes. This updates the beta branch but does not publish a beta package.

Starefossen and others added 3 commits September 10, 2026 08:33
## Summary
- create a reviewable sync PR from main to beta after each main push
- run the ci-ok check for pull requests targeting beta
- document beta synchronization and protection requirements

## Validation
- actionlint
- git diff --check

The beta ruleset could not be created from this session because GitHub
API write operations are blocked by the sandbox.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
## Summary
- restrict beta manual publishing to workflow dispatches run from the
beta branch
- document the required beta-branch dispatch

Supersedes #46, which conflicts because #45 was squash-merged.

## Validation
- actionlint
- git diff --check

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
## Summary
- document stable-only and beta-first release flows
- document how to resolve beta synchronization release-state conflicts
- restore repository scoping and explicit GitHub CLI failure handling in
the beta sync workflow

## Validation
- actionlint
- git diff --check

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI lite review requested due to automatic review settings September 10, 2026 09:16

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The manual workflow_dispatch path for the beta publish job is likely skipped due to needs on a job that is skipped, preventing intended manual re-publishing.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Updates the project’s beta-branch maintenance flow by automating creation of a “sync main into beta” PR and documenting stable/beta release procedures, while tightening CI and beta release workflow conditions.

Changes:

  • Document stable vs. beta release flows and how/when to sync main into beta (RELEASING.md).
  • Add a workflow that opens a PR from main into beta on each push to main (sync-beta.yml).
  • Ensure CI runs for PRs targeting beta and pin key GitHub Actions to SHAs (ci.yaml), and restrict manual beta publish runs to the beta branch (release-please-beta.yml).
File summaries
File Description
RELEASING.md Expands guidance for stable and beta release workflows and synchronization handling.
.github/workflows/sync-beta.yml Adds automation to open a sync PR from main into beta on main pushes.
.github/workflows/release-please-beta.yml Adjusts publish gating logic for beta releases and manual dispatch constraints.
.github/workflows/ci.yaml Runs CI on PRs to beta and pins Actions to specific commit SHAs.
Review details
  • Files reviewed: 4/4 changed files
  • Comments generated: 1
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +39 to +42
if: >-
!cancelled() &&
(needs.release-please.outputs.releases_created == 'true' || github.event_name == 'workflow_dispatch')
(needs.release-please.outputs.releases_created == 'true' ||
(github.event_name == 'workflow_dispatch' && github.ref == 'refs/heads/beta'))
@Starefossen

Copy link
Copy Markdown
Member

Superseded by #54. The original PR sources protected main, so conflicts cannot be resolved on its head branch.

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.

2 participants