V2

[dev-davexoyinbo]

No description provided.

[qodo-code-review]

Review Summary by Qodo

Add conventional commits support to semantic release

✨ Enhancement

Walkthroughs

Description

• Add conventional commits preset to semantic-release plugins
• Configure commit-analyzer with conventionalcommits preset
• Configure release-notes-generator with conventionalcommits preset
• Bump package version to 2.0.0
• Minor formatting adjustments in configuration

Diagram

flowchart LR
  A["release.config.js"] -->|"Add conventionalcommits preset"| B["commit-analyzer plugin"]
  A -->|"Add conventionalcommits preset"| C["release-notes-generator plugin"]
  D["package.json"] -->|"Update version"| E["2.0.0"]

Loading

File Changes

1. release.config.js ⚙️ Configuration changes +15/-8

Configure conventional commits for semantic release

• Wrapped commit-analyzer plugin with configuration object containing conventionalcommits preset
• Added release-notes-generator plugin configuration with conventionalcommits preset
• Reformatted assets array in git plugin for consistency
• Updated changelog plugin configuration formatting

release.config.js

---

2. package.json Other +1/-1

Bump version to 2.0.0

• Updated version from 1.x.x to 2.0.0
• Minor whitespace adjustment in description field

package.json

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0)

1. Duplicate notes generator 🐞 Bug ≡ Correctness

Description

release.config.js includes @semantic-release/release-notes-generator twice (one configured with
preset, one unconfigured), so the generateNotes step will run twice and can duplicate/override
release notes written to the changelog/GitHub release.

Code

release.config.js[R10-16]

Evidence

The release config shows two release-notes-generator entries, and CI runs semantic-release using
this config; therefore generateNotes will execute twice with different configuration (preset vs
default).

release.config.js[10-16]
.github/workflows/main.yml[37-59]
.github/workflows/versioned.yml[37-59]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`release.config.js` configures `@semantic-release/release-notes-generator` with the `conventionalcommits` preset, but also leaves a second unconfigured `@semantic-release/release-notes-generator` entry in the plugins list. This results in the `generateNotes` phase being executed twice, potentially producing duplicated or inconsistent release notes.

### Issue Context
CI runs `npx semantic-release`, which loads `release.config.js` by default.

### Fix Focus Areas
- release.config.js[10-16]

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

---

2. v2 branch not configured 🐞 Bug ☼ Reliability

Description

CI runs semantic-release on v* branches, but release.config.js only declares v1 (plus main) as
release branches, so pushes on v2 will not follow the intended versioned-branch release channel
configuration.

Code

release.config.js[2]

Evidence

The versioned workflow triggers on v* branches and runs semantic-release, while release.config.js
only configures v1 and main as release branches; this configuration mismatch directly impacts
releases from v2.

.github/workflows/versioned.yml[3-7]
.github/workflows/versioned.yml[37-56]
release.config.js[1-3]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The workflow triggers semantic-release on any `v*` branch, but `release.config.js` only lists `{ name: "v1", channel: "v1" }` and `main`. This mismatch means `v2` pushes won’t be treated as a configured release branch/channel.

### Issue Context
`versioned.yml` runs on `v*` branches and executes `npx semantic-release`.

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

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

---

[qodo-code-review]

1. Duplicate notes generator 🐞 Bug ≡ Correctness

release.config.js includes @semantic-release/release-notes-generator twice (one configured with
preset, one unconfigured), so the generateNotes step will run twice and can duplicate/override
release notes written to the changelog/GitHub release.

Agent Prompt

### Issue description
`release.config.js` configures `@semantic-release/release-notes-generator` with the `conventionalcommits` preset, but also leaves a second unconfigured `@semantic-release/release-notes-generator` entry in the plugins list. This results in the `generateNotes` phase being executed twice, potentially producing duplicated or inconsistent release notes.

### Issue Context
CI runs `npx semantic-release`, which loads `release.config.js` by default.

### Fix Focus Areas
- release.config.js[10-16]

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

[qodo-code-review]

2. V2 branch not configured 🐞 Bug ☼ Reliability

CI runs semantic-release on v* branches, but release.config.js only declares v1 (plus main) as
release branches, so pushes on v2 will not follow the intended versioned-branch release channel
configuration.

Agent Prompt

### Issue description
The workflow triggers semantic-release on any `v*` branch, but `release.config.js` only lists `{ name: "v1", channel: "v1" }` and `main`. This mismatch means `v2` pushes won’t be treated as a configured release branch/channel.

### Issue Context
`versioned.yml` runs on `v*` branches and executes `npx semantic-release`.

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

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

[github-actions]

🎉 This PR is included in version 2.0.0 🎉

The release is available on:

• npm package (@main dist-tag)
• GitHub release

Your semantic-release bot 📦🚀