Skip to content
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.

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

fix(release-please): use correct gh token #500

Merged
merged 1 commit into from
Feb 28, 2024
Merged

Conversation

arealmaas
Copy link
Collaborator

The GITHUB_TOKEN will not be able to trigger any github action runs, therefore we need to create a custom PAT to use.

https://github.com/google-github-actions/release-please-action?tab=readme-ov-file#github-credentials

@arealmaas arealmaas merged commit ebff656 into main Feb 28, 2024
13 checks passed
@arealmaas arealmaas deleted the fix/use-correct-gh-token branch February 28, 2024 10:45
Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

arealmaas added a commit that referenced this pull request Feb 28, 2024
🤖 I have created a release *beep* *boop*
---


##
[1.0.2](v1.0.1...v1.0.2)
(2024-02-28)


### Bug Fixes

* always run staging dry-runs in release-please-pr
([3e390e7](3e390e7))
* fix workflow permissions
([40e5485](40e5485))
* fix workflow permissions
([b2213b2](b2213b2))
* **release-please:** use correct gh token
([#500](#500))
([ebff656](ebff656))
* use temporary gh token
([c1118ae](c1118ae))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant