Skip to content

fix: update semantic-release branches to main and v1 #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dev-davexoyinbo merged 1 commit into from
May 25, 2026
Merged

fix: update semantic-release branches to main and v1 #44

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion release.config.js
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
export default {
branches: ["release"],
branches: [{ name: "v1", channel: "v1" }, "main"],
Copy link
Copy Markdown

@qodo-code-review qodo-code-review Bot May 25, 2026

Choose a reason for hiding this comment

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

Action required

1. Branch config/workflow mismatch 🐞 Bug ≡ Correctness

.github/workflows/versioned.yml runs npx semantic-release on every v* branch push, but
release.config.js only allows releases from v1 and main, so release jobs on branches like v2
will no-op (no publish/tag) even though CI executes the release step.
Agent Prompt 
## Issue description
The CI `Versioned` workflow triggers on `v*` branches and executes `semantic-release`, but `semantic-release` is configured to only release from `v1` and `main`. This causes release runs on other `v*` branches to succeed without publishing anything.

## Issue Context
- `versioned.yml` triggers for all `v*` branches and runs `npx semantic-release`.
- `release.config.js` restricts semantic-release branches to `v1` and `main`.

## Fix Focus Areas
- release.config.js[1-3]
- .github/workflows/versioned.yml[3-8]
- .github/workflows/versioned.yml[37-59]

## Proposed fix
Decide the intended release sources:
- If you want releases from multiple `vN` branches: update `release.config.js` to include those branches (e.g., add `v2` / additional maintenance branch definitions).
- If you only want releases from `v1` and `main`: narrow `.github/workflows/versioned.yml` triggers/conditions so it only runs the release job for `v1` (and/or remove the release job from `versioned.yml` for other `v*` branches).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

plugins: [
"@semantic-release/commit-analyzer",
"@semantic-release/release-notes-generator",
Expand Down
Loading