Skip to content

fix: pipe the token #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jaronoff97 merged 1 commit into from
May 29, 2026
Merged

fix: pipe the token #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 1 addition & 6 deletions .github/workflows/tero-release-please.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,11 +41,6 @@ jobs:
owner: ${{ github.repository_owner }}
- uses: googleapis/release-please-action@5c625bfb5d1ff62eadeeb3772007f7f66fdcf071 # v4.4.1
with:
# GITHUB_TOKEN works, but PRs it creates cannot trigger other
# workflows. If you want `tero-release.yaml` to fire when the
# release PR is merged (and the tag is pushed automatically), swap
# this for a PAT or GitHub App token. Today the tag push DOES
# trigger workflows because release-please pushes it directly.
token: ${{ secrets.GITHUB_TOKEN }}
token: ${{ steps.generate-token.outputs.token }}
config-file: release-please-config.json
manifest-file: .release-please-manifest.json
Loading