Tracking issue for the dev → main release that release-please will tag as v0.2.15 (pre-1.0 PATCH bump; 49 commits since v0.2.14, all feat:/fix:, no breaking changes).
User-facing changes since v0.2.14
Process
- dev → main PR titled
feat(release): so the merge-commit subject triggers the release-please bump.
- Merge the release-please Release PR on
main to tag v0.2.15.
- Back-merge
main → dev with a merge commit.
Tracking issue for the
dev→mainrelease that release-please will tag as v0.2.15 (pre-1.0 PATCH bump; 49 commits since v0.2.14, allfeat:/fix:, no breaking changes).User-facing changes since v0.2.14
/explain/{forecast,runs,jobs}+ ExplanationPanel UI (Forecast Explainability & Driver Attribution slice #224)scenariosslice #221)fix(ui): parseapplication/problem+jsonerror bodies (fix(ui): api client never parses application/problem+json error bodies #230)Process
feat(release):so the merge-commit subject triggers the release-please bump.mainto tagv0.2.15.main→devwith a merge commit.