Update ci.yml

[guibranco]

📑 Description

Closes #280

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• All the tests have passed

☢️ Does this introduce a breaking change?

• Yes
• No

---

Summary by Sourcery

Update CI workflow to publish both full semantic version and major-version GitHub releases when distribution changes or the workflow is manually dispatched.

Build:

• Adjust release step naming to clarify that the primary tag uses the full semantic version.
• Add a second release step to create and publish a major-version (v) GitHub release tag alongside the full semantic version release.

CI:

• Extend the CI release workflow to generate and update a major-version release tag in addition to the existing full semantic version tag.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR adjusts the CI workflow to produce two types of GitHub releases from GitVersion output: a full semantic version release and an additional major-version-only release tag, without changing triggering conditions.

File-Level Changes

Change	Details	Files
Extend release workflow to create both full semantic version and major-only GitHub releases from GitVersion output.	Rename the existing release job step to clarify that it uses the full semantic version (fullSemVer) for the tag and name. Add a second release-action step that runs under the same conditions to create or update a major-version-only tag (v) and corresponding release. Configure the new major-version release to allow updates, always generate release notes, and to not mark the release as latest.	.github/workflows/ci.yml

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#280	Add automation so that on release, a major-version tag (e.g., v1) is created or updated to point to the latest release of that major version, enabling users to reference the action as @v1.	✅

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Warning

Rate limit exceeded

@guibranco has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 2 minutes and 12 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b383d208-6e92-482e-b7fc-fcc14705c5b6

📥 Commits

Reviewing files that changed from the base of the PR and between f695229 and 1e94158.

📒 Files selected for processing (1)

• .github/workflows/ci.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch guibranco-patch-1

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[sonarqubecloud]

Quality Gate failed

Failed conditions
1 Security Hotspot

See analysis details on SonarQube Cloud

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[sourcery-ai]

Hey - I've left some high level feedback:

• The new major-version release step duplicates most of the configuration from the fullSemVer release step; consider extracting shared settings via a reusable action or YAML anchors to reduce maintenance overhead and keep the two in sync.
• The Update latest tag step only checks steps.create_release.outputs.id, so if the major-version release runs but the fullSemVer one is skipped or fails, the latest tag logic might not behave as expected; consider clarifying which release step should drive the latest tag update or aggregating their outputs explicitly.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The new major-version release step duplicates most of the configuration from the fullSemVer release step; consider extracting shared settings via a reusable action or YAML anchors to reduce maintenance overhead and keep the two in sync.
- The `Update latest tag` step only checks `steps.create_release.outputs.id`, so if the major-version release runs but the fullSemVer one is skipped or fails, the latest tag logic might not behave as expected; consider clarifying which release step should drive the `latest` tag update or aggregating their outputs explicitly.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[penify-dev]

Failed to generate code suggestions for PR