chore(repo): back-merge main into dev after v0.2.16 release (#252)#255
Conversation
feat(release): ship the MLZOO advanced ML model zoo (A–C2) to main (#252)
…n--components--forecastlabai chore(main): release 0.2.16
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
|
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 |
Brings the v0.2.16 release commits from
mainback intodevso the nextdev → mainrelease PR doesn't conflict onCHANGELOG.md/.release-please-manifest.json/pyproject.toml.What this brings to dev:
7f7bd15— Merge PR chore(main): release 0.2.16 #254 (release 0.2.16)e54b44a—docs(docs): capitalize XGBoost in v0.2.16 changelog entry2778c0f—chore(main): release 0.2.16(CHANGELOG + manifest + pyproject0.2.15 → 0.2.16)689ac94— Merge PR feat(release): ship the MLZOO advanced ML model zoo (A–C2) to main (#252) #253 (dev → main)Diff: 3 files changed —
CHANGELOG.md(+35),.release-please-manifest.json(0.2.15 → 0.2.16),pyproject.toml(0.2.15 → 0.2.16).Merge instruction:⚠️ Must be merged with
--merge(a real merge commit), never squashed — otherwise main never becomes a dev ancestor and the next dev→main release PR keeps re-conflicting. Seedocs/_base/RUNBOOKS.mdand the prior back-merge memory.Refs #252.