Skip to content

chore(release): back-merge v0.2.20 into dev#328

Merged
w7-mgfcode merged 3 commits into
devfrom
chore/back-merge-v0.2.20
May 31, 2026
Merged

chore(release): back-merge v0.2.20 into dev#328
w7-mgfcode merged 3 commits into
devfrom
chore/back-merge-v0.2.20

Conversation

@w7-mgfcode
Copy link
Copy Markdown
Owner

@w7-mgfcode w7-mgfcode commented May 31, 2026

Purpose

Sync dev with the v0.2.20 release commit from main. The release-please version/changelog/manifest bump lives only on main; this back-merge carries it into dev so dev reports 0.2.20 and future dev → main release PRs don't re-conflict on release metadata.

Includes

Net diff vs dev is only the release metadata produced by release-please:

  • .release-please-manifest.json0.2.20
  • pyproject.tomlversion = "0.2.20"
  • CHANGELOG.md → new [0.2.20] section

(Underlying feature commits were already on dev; they reached main via PR #326.)

Validation

  • uv run ruff format --check . — passed (333 files already formatted)
  • uv run ruff check . — passed (All checks passed!)

⚠️ Merge instruction

Merge this PR with a MERGE COMMIT — NOT squash. A squash would prevent main from becoming an ancestor of dev, causing subsequent dev → main release PRs to keep re-conflicting. (See project convention: back-merge needs a merge commit.)

Summary by Sourcery

Back-merge the v0.2.20 release metadata into the development branch so it reports the correct release version.

Build:

  • Update project version to 0.2.20 in pyproject configuration.
  • Align release-please manifest version with the v0.2.20 release.

Documentation:

  • Add changelog entry documenting the 0.2.20 release features, fixes, and documentation updates.

Chores:

  • Synchronize dev branch with main by incorporating the v0.2.20 release changelog and version metadata.

release: promote dev to main for v0.2.20
…n--components--forecastlabai

chore(main): release 0.2.20
@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented May 31, 2026

Reviewer's Guide

Back-merges the v0.2.20 release metadata from main into dev so dev reports version 0.2.20 and contains the corresponding changelog section, relying entirely on release-please outputs and preserving history via a merge commit.

Flow diagram for back-merge of release metadata into dev

flowchart LR
    MainBranch[main v0.2.20]
    DevBranch[dev]
    ReleasePlease[release_please]
    Manifest[.release_please_manifest.json]
    Pyproject[pyproject.toml version 0.2.20]
    Changelog[CHANGELOG.md 0.2.20]

    ReleasePlease --> MainBranch
    MainBranch --> Manifest
    MainBranch --> Pyproject
    MainBranch --> Changelog

    MainBranch -- back_merge_merge_commit --> DevBranch
    DevBranch --> Manifest
    DevBranch --> Pyproject
    DevBranch --> Changelog
Loading

File-Level Changes

Change Details Files
Align dev branch release metadata with v0.2.20 release from main.
  • Add a new 0.2.20 section to the changelog including features, bug fixes, and documentation items generated by release-please.
  • Bump the project version string from 0.2.19 to 0.2.20 in the Python project configuration.
  • Update the release-please manifest to record 0.2.20 as the current release version for the repository.
CHANGELOG.md
pyproject.toml
.release-please-manifest.json

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

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 31, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2d10a706-8ced-43ee-8fe6-dccdd358b21a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/back-merge-v0.2.20

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

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

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

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 new 0.2.20 changelog section contains several duplicate lines for the same issue/feature (e.g., repeated entries for #309, #315, #321, #302, #305, #312, #313, #295), so consider deduplicating these to keep the release notes concise and easier to scan.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The new 0.2.20 changelog section contains several duplicate lines for the same issue/feature (e.g., repeated entries for #309, #315, #321, #302, #305, #312, #313, #295), so consider deduplicating these to keep the release notes concise and easier to scan.

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.

@w7-mgfcode w7-mgfcode merged commit 4824f49 into dev May 31, 2026
15 checks passed
@w7-mgfcode w7-mgfcode deleted the chore/back-merge-v0.2.20 branch May 31, 2026 19:12
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.

1 participant