From a2592bf2b07692432815b04461ed714eeda32f19 Mon Sep 17 00:00:00 2001 From: Sameeul B Samee Date: Thu, 16 Jul 2026 17:29:16 -0400 Subject: [PATCH] ci(release-please): use manifest config so 0.x breaking = minor, and pin 0.12.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The release PR (#344) proposed 1.0.0 because the workflow drove release-please-action@v4 with inline release-type/package-name, which put v4 on the non-manifest path and ignored release-please-config.json — where bump-minor-pre-major:true already asks for 0.x breaking changes to bump the minor (0.11.0 -> 0.12.0), not jump to 1.0.0. Switch to config-file/manifest-file so the policy is honored. Also pin this release explicitly via the footer below in case the config wiring needs a cycle to take effect. (The prior empty-commit Release-As in #376 was dropped by rebase-merge and never reached main; this carries the footer on a real change so it survives any merge.) Release-As: 0.12.0 Co-Authored-By: Claude Opus 4.8 (1M context) --- .github/workflows/release-please.yml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/.github/workflows/release-please.yml b/.github/workflows/release-please.yml index b8b4d794..600de0cc 100644 --- a/.github/workflows/release-please.yml +++ b/.github/workflows/release-please.yml @@ -20,8 +20,12 @@ jobs: - uses: google-github-actions/release-please-action@v4 id: release with: - release-type: python - package-name: nyxus + # Use the manifest config so release-please honors bump-minor-pre-major + # (0.x breaking changes -> minor, not a jump to 1.0.0). release-type/ + # package-name live in release-please-config.json; passing them inline put + # v4 on the non-manifest path and silently ignored the config. + config-file: release-please-config.json + manifest-file: .release-please-manifest.json - name: Checkout code if: ${{ steps.release.outputs.release_created }}