chore(repo): back-merge main → dev (v0.2.19)#294
Conversation
release: cut v0.2.19 (PRP-34 batch parallel execution)
…n--components--forecastlabai chore(main): release 0.2.19
|
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 |
Reviewer's guide (collapsed on small PRs)Reviewer's GuideBack-merge of the 0.2.19 release bump from main into dev, updating version metadata and changelog so dev’s history matches the released main branch. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub. |
Summary
Standard post-release back-merge so
mainbecomes an ancestor ofdevagain. Brings the release-please version-bump commit (chore(main): release 0.2.19,f6c93cd) intodev.Test plan
--merge(NOT--squash) per theback-merge-needs-merge-commitmemory — squashing leavesmainun-ancestored todevand the next dev→main release PR will re-conflict onCHANGELOG.md/pyproject.toml/.release-please-manifest.json.git log --oneline origin/main..origin/devshows zero divergence on the version bump commit.Summary by Sourcery
Back-merge the 0.2.19 release changes from main into dev to realign branches and include the latest release metadata.
New Features:
Enhancements:
Documentation: