Skip to content

fix: correct Release Please branch name in release workflow#410

Merged
Aureliolo merged 1 commit intomainfrom
fix/release-rp-branch
Mar 14, 2026
Merged

fix: correct Release Please branch name in release workflow#410
Aureliolo merged 1 commit intomainfrom
fix/release-rp-branch

Conversation

@Aureliolo
Copy link
Copy Markdown
Owner

Summary

The BSL Change Date auto-update step was checking out release-please--branches--main, but Release Please uses release-please--branches--main--components--synthorg (component suffix from release-please-config.json). One-line fix.

Test plan

  • Verified actual RP branch name from CI logs: release-please--branches--main--components--synthorg
  • YAML validates

The RP branch includes the component suffix:
release-please--branches--main--components--synthorg
Copilot AI review requested due to automatic review settings March 14, 2026 18:30
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

@github-actions
Copy link
Copy Markdown
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 14, 2026

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: acb1d26c-7d60-47cd-bb77-f109dc22b74a

📥 Commits

Reviewing files that changed from the base of the PR and between cabe953 and 8065bc9.

📒 Files selected for processing (1)
  • .github/workflows/release.yml

📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Updated internal release workflow configuration to reference the correct branch.

Walkthrough

The GitHub Actions release workflow is updated to change the branch reference from release-please--branches--main to release-please--branches--main--components--synthorg in the Checkout Release PR branch step.

Changes

Cohort / File(s) Summary
GitHub Actions Workflow
.github/workflows/release.yml
Updated branch reference in the Checkout Release PR branch step from release-please--branches--main to release-please--branches--main--components--synthorg.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/release-rp-branch
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch fix/release-rp-branch
📝 Coding Plan
  • Generate coding plan for human review comments

Comment @coderabbitai help to get the list of available commands and usage tips.

@Aureliolo Aureliolo merged commit 515d816 into main Mar 14, 2026
25 of 26 checks passed
@Aureliolo Aureliolo deleted the fix/release-rp-branch branch March 14, 2026 18:30
@greptile-apps
Copy link
Copy Markdown

greptile-apps bot commented Mar 14, 2026

Greptile Summary

This PR fixes a broken BSL Change Date auto-update step in the release workflow by correcting the Release Please branch name from the generic release-please--branches--main to the component-qualified release-please--branches--main--components--synthorg, which matches the package-name: "synthorg" entry in .github/release-please-config.json.

  • The old ref (release-please--branches--main) would cause the actions/checkout step to fail silently or check out the wrong branch whenever Release Please created or updated a release PR, meaning the BSL Change Date would never actually be committed to the release branch.
  • The corrected ref (release-please--branches--main--components--synthorg) matches the actual branch Release Please creates when a component suffix is configured, so the subsequent sed/git push steps will now operate on the right branch.
  • No other logic in the workflow was changed; the fix is minimal and correct.

Confidence Score: 5/5

  • This PR is safe to merge — it is a single-line targeted correction to a workflow branch ref with no risk of regression.
  • The change is a one-line fix correcting a literal string (the Release Please branch ref) that was demonstrably wrong based on the component configuration in release-please-config.json. The fix aligns with Release Please's documented branch naming convention (release-please--branches--{base}--components--{package-name}), no logic was altered, and the rest of the workflow is unchanged.
  • No files require special attention.

Important Files Changed

Filename Overview
.github/workflows/release.yml Corrects the Release Please branch ref from the generic release-please--branches--main to the component-specific release-please--branches--main--components--synthorg, matching the package-name defined in release-please-config.json. Fix is accurate and aligns with Release Please's branch naming convention.

Last reviewed commit: 8065bc9

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Fixes the release workflow’s checkout ref so the “Update BSL Change Date” step targets the actual Release Please PR branch name used by this repo’s manifest/component configuration.

Changes:

  • Update the actions/checkout ref to include the Release Please component suffix (--components--synthorg).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
with:
ref: release-please--branches--main # must match the repo default branch name
ref: release-please--branches--main--components--synthorg
Aureliolo added a commit that referenced this pull request Mar 15, 2026
🤖 I have created a release *beep* *boop*
---


##
[0.2.0](v0.1.4...v0.2.0)
(2026-03-15)

##First probably usable release? Most likely not no and everything will break
### Features

* add /get/ installation page for CLI installer
([#413](#413))
([6a47e4a](6a47e4a))
* add cross-platform Go CLI for container lifecycle management
([#401](#401))
([0353d9e](0353d9e)),
closes [#392](#392)
* add explicit ScanOutcome signal to OutputScanResult
([#394](#394))
([be33414](be33414)),
closes [#284](#284)
* add meeting scheduler, event-triggered meetings, and Go CLI lint fixes
([#407](#407))
([5550fa1](5550fa1))
* wire MultiAgentCoordinator into runtime
([#396](#396))
([7a9e516](7a9e516))


### Bug Fixes

* CLA signatures branch + declutter repo root
([#409](#409))
([cabe953](cabe953))
* correct Release Please branch name in release workflow
([#410](#410))
([515d816](515d816))
* replace slsa-github-generator with attest-build-provenance, fix DAST
([#424](#424))
([eeaadff](eeaadff))
* resolve CodeQL path-injection alerts in Go CLI
([#412](#412))
([f41bf16](f41bf16))


### Refactoring

* rename package from ai_company to synthorg
([#422](#422))
([df27c6e](df27c6e)),
closes [#398](#398)


### Tests

* add fuzz and property-based testing across all layers
([#421](#421))
([115a742](115a742))


### CI/CD

* add SLSA L3 provenance for CLI binaries and container images
([#423](#423))
([d3dc75d](d3dc75d))
* bump the major group with 4 updates
([#405](#405))
([20c7a04](20c7a04))


### Maintenance

* bump github.com/spf13/cobra from 1.9.1 to 1.10.2 in /cli in the
minor-and-patch group
([#402](#402))
([e31edbb](e31edbb))
* narrow BSL Additional Use Grant and add CLA
([#408](#408))
([5ab15bd](5ab15bd)),
closes [#406](#406)

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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