chore: back-merge main into dev after v0.2.23 release#424
Conversation
Release showcase workspace completion (E1–E6, umbrella #406). release-please bumps v0.2.22 → v0.2.23.
…n--components--forecastlabai chore(main): release 0.2.23
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 |
Back-merge the release-please
v0.2.23commit (version bump in.release-please-manifest.json+pyproject.toml+CHANGELOG.md) frommainintodev.Keeps
mainan ancestor ofdevso the nextdev → mainrelease PR does not re-conflict. Merge with--merge(a merge commit) — never squash (repo back-merge invariant).