From 467acad0e4497993c8ba784502cec1d5752a39b5 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 21 Nov 2025 18:25:33 +0000 Subject: [PATCH 1/2] Initial plan From 805c21eb69e97dc43e13940d3899c79d9f8ec422 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 21 Nov 2025 18:27:52 +0000 Subject: [PATCH 2/2] Update release-please.yml to use secrets.GITHUB_TOKEN Co-authored-by: NoopDog <3239697+NoopDog@users.noreply.github.com> --- .github/workflows/release-please.yml | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/.github/workflows/release-please.yml b/.github/workflows/release-please.yml index b222da4c9..c382a9403 100644 --- a/.github/workflows/release-please.yml +++ b/.github/workflows/release-please.yml @@ -2,6 +2,7 @@ on: push: branches: - main + workflow_dispatch: # Enable manual triggering permissions: contents: write @@ -17,8 +18,4 @@ jobs: id: release with: config-file: release-please-config.json - # this assumes that you have created a personal access token - # (PAT) and configured it as a GitHub action secret named - # `MY_RELEASE_PLEASE_TOKEN` (this secret name is not important). - token: ${{ secrets.HCA_RELEASE_PLEASE_TOKEN }} - # This is a built-in strategy in release-please, see "Action Inputs" for more options + token: ${{ secrets.GITHUB_TOKEN }}