From 696c5b120d792e3cd52139a9ac4708c4fe464b5a Mon Sep 17 00:00:00 2001 From: Vladimir Berezhnoy Date: Sat, 26 Sep 2026 09:06:44 -0400 Subject: [PATCH] feat: pass a package-name input through to release-please-forecast release-please-forecast (non7top/release-please-forecast#21) added a package-name input so it can classify the predicted bump against a manifest keyed by package path instead of ".", which a cargo-workspace + linked-versions setup produces. This reusable workflow hardcoded no such input, so a caller had no way to set it. Thread it through. --- .github/workflows/release-please-preview.yml | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/.github/workflows/release-please-preview.yml b/.github/workflows/release-please-preview.yml index d01b10f..3a1f732 100644 --- a/.github/workflows/release-please-preview.yml +++ b/.github/workflows/release-please-preview.yml @@ -1,7 +1,21 @@ name: release-please-preview on: - workflow_call: {} + workflow_call: + inputs: + package-name: + description: >- + Passed straight through to release-please-forecast's own + package-name input. Leave unset for a repo whose + .release-please-manifest.json is keyed by ".". Required for a + repo split into per-directory packages (release-please's + cargo-workspace/linked-versions plugins, say) unless every + package in the manifest is kept at the same version by a + linked-versions group with merge: true, in which case + release-please-forecast's own first-key fallback covers it — + see that action's README. + type: string + default: '' permissions: contents: read @@ -25,3 +39,4 @@ jobs: - uses: non7top/release-please-forecast@v1 with: github-token: ${{ secrets.GITHUB_TOKEN }} + package-name: ${{ inputs.package-name }}