Skip to content

build(release): release 2.0.11 and bump to next development version#116

Merged
ruromero merged 2 commits into
mainfrom
release/v2.0.11
Jul 7, 2026
Merged

build(release): release 2.0.11 and bump to next development version#116
ruromero merged 2 commits into
mainfrom
release/v2.0.11

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown

This PR contains the following changes:

  1. Release version bump to 2.0.11.
  2. Filtered resources (docs, JS) updated to reflect the release version.
  3. Next development version bump after the release.

Summary by Sourcery

Bump project to the next snapshot development version after the 2.0.11 release.

Build:

  • Update Maven project version to 2.0.12-SNAPSHOT.

Documentation:

  • Update README usage examples to reference version 2.0.12-SNAPSHOT.

@sourcery-ai

sourcery-ai Bot commented Jul 7, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Bumps project and documentation versions from 2.0.11-SNAPSHOT to 2.0.12-SNAPSHOT to reflect the new 2.0.11 release and next development iteration, and aligns Maven and npm usage instructions accordingly.

File-Level Changes

Change Details Files
Update Maven artifact version to the next SNAPSHOT after the 2.0.11 release.
  • Changed the project version from 2.0.11-SNAPSHOT to 2.0.12-SNAPSHOT in the main Maven POM to start the next development iteration.
pom.xml
Align README dependency examples with the new SNAPSHOT version.
  • Updated the Maven dependency snippet to reference 2.0.12-SNAPSHOT instead of 2.0.11-SNAPSHOT.
  • Updated the npm install command example to use 2.0.12-SNAPSHOT instead of 2.0.11-SNAPSHOT.
README.md

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

@sourcery-ai sourcery-ai Bot 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.

Hey - I've left some high level feedback:

  • The PR title and description mention releasing 2.0.11, but all visible changes bump to 2.0.12-SNAPSHOT; double-check that the actual 2.0.11 release version (non-SNAPSHOT) is set and committed where needed to keep the release process consistent.
  • Ensure that any other references to the previous snapshot or release version (e.g., in build scripts or additional docs) are updated to 2.0.12-SNAPSHOT to avoid version drift between modules or consumers.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The PR title and description mention releasing 2.0.11, but all visible changes bump to 2.0.12-SNAPSHOT; double-check that the actual 2.0.11 release version (non-SNAPSHOT) is set and committed where needed to keep the release process consistent.
- Ensure that any other references to the previous snapshot or release version (e.g., in build scripts or additional docs) are updated to 2.0.12-SNAPSHOT to avoid version drift between modules or consumers.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.00%. Comparing base (ffca6de) to head (484d818).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff            @@
##               main     #116   +/-   ##
=========================================
  Coverage     95.00%   95.00%           
  Complexity       35       35           
=========================================
  Files             4        4           
  Lines           100      100           
  Branches          9        9           
=========================================
  Hits             95       95           
  Misses            4        4           
  Partials          1        1           
Flag Coverage Δ
unit-tests 95.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@ruromero ruromero merged commit 683926c into main Jul 7, 2026
4 checks passed
@ruromero ruromero deleted the release/v2.0.11 branch July 7, 2026 08:49
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