chore(release): back-merge v0.2.20 into dev#328
Conversation
release: promote dev to main for v0.2.20
…n--components--forecastlabai chore(main): release 0.2.20
Reviewer's GuideBack-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 devflowchart 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
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
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.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
Purpose
Sync
devwith the v0.2.20 release commit frommain. The release-please version/changelog/manifest bump lives only onmain; this back-merge carries it intodevsodevreports0.2.20and futuredev → mainrelease PRs don't re-conflict on release metadata.Includes
Net diff vs
devis only the release metadata produced by release-please:.release-please-manifest.json→0.2.20pyproject.toml→version = "0.2.20"CHANGELOG.md→ new[0.2.20]section(Underlying feature commits were already on
dev; they reachedmainvia PR #326.)Validation
uv run ruff format --check .— passed (333 files already formatted)uv run ruff check .— passed (All checks passed!)Merge this PR with a MERGE COMMIT — NOT squash. A squash would prevent
mainfrom becoming an ancestor ofdev, causing subsequentdev → mainrelease 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:
Documentation:
Chores: