chore(repo): back-merge main into dev after v0.2.17 release (#270)#271
Conversation
release: prepare v0.2.17 — MLZOO-D + dogfood automation + cross-slice import pattern
…n--components--forecastlabai chore(main): release 0.2.17
|
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.
Sorry @w7-mgfcode, you have reached your weekly rate limit of 500000 diff characters.
Please try again later or upgrade to continue using Sourcery
Post-release back-merge for v0.2.17.
Closes #270.
Per memory `back-merge-needs-merge-commit` and the v0.2.16 precedent (#255):
gh pr merge 271 --merge # ← when CI is green; do NOT use --squash / --rebaseSquashing the back-merge flattens the two-parent merge commit so
mainnever becomes an ancestor ofdev, and the nextdev → mainrelease PR keeps re-conflicting on the release-please version files.What's in this PR
The diff is exactly the release-please commit on
mainfor v0.2.17:CHANGELOG.md—## [0.2.17]sectionpyproject.toml— version bump.release-please-manifest.json—".":"0.2.17"Nothing else. No new feature work.
Verify after merge