From 4798d0644b9a79317435708ac69ab4727c9cf64e Mon Sep 17 00:00:00 2001 From: Peter Corke Date: Fri, 3 Jul 2026 17:54:13 +1000 Subject: [PATCH] docs: record 1.3.1 in release-please manifest and CHANGELOG The 1.3.1 rtb-data-pin release was published out-of-band from a maintenance branch off the v1.3.0 tag (main had already diverged with in-progress work), so release-please's own bookkeeping never saw it. Without this, release-please could later try to reuse the v1.3.1 tag for a from-main release and collide with the one that already shipped. Co-Authored-By: Claude Sonnet 5 --- .github/.release-please-manifest.json | 2 +- CHANGELOG.md | 16 ++++++++++++++++ 2 files changed, 17 insertions(+), 1 deletion(-) diff --git a/.github/.release-please-manifest.json b/.github/.release-please-manifest.json index 6a7753e33..3b3e5e7bd 100644 --- a/.github/.release-please-manifest.json +++ b/.github/.release-please-manifest.json @@ -1,3 +1,3 @@ { - ".": "1.3.0" + ".": "1.3.1" } \ No newline at end of file diff --git a/CHANGELOG.md b/CHANGELOG.md index 9c67283b5..7ab03677a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,21 @@ # Changelog +## [1.3.1](https://github.com/petercorke/robotics-toolbox-python/compare/v1.3.0...v1.3.1) (2026-07-03) + +Manual out-of-band release from the `v1.3.0` tag (not via release-please — +`main` has since diverged with in-progress, breaking work). See +`tech-debt.md` ("Release process: single-branch release-please + stacked +PRs on a red `main`") for why. + +### Bug Fixes + +* **deps:** pin `rtb-data<2` to protect this release line from an upcoming + breaking `rtb-data` reorganisation (renamed/deleted model folders) that + will ship as `rtb-data` 2.0 alongside the next `roboticstoolbox-python` + major/minor release. Without this pin, any fresh `pip install + roboticstoolbox-python` would silently pick up the incompatible new + `rtb-data` and fail to load bundled robot models. + ## [1.3.0](https://github.com/petercorke/robotics-toolbox-python/compare/v1.2.0...v1.3.0) (2026-06-14)