You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A hopefully simple question about the refresh token. If I understand correctly, a refresh token can expire, but can be used to obtain a new refresh token. I'm concerned that when the refresh token expires, the deploy process will fail in my Github Action because the action isn't able to update the refresh token that I'm storing in my repo's secrets. Is this a valid concern? If yes, how should I handle this?
Issue
I have searched the issues of this repository and believe that this is not a duplicate.
Your Environment
Github Action
semantic-release-chrome version: 3.2.0
node version: v2.0
npm (or yarn) version: 4.1.1
Relevant code or config
name: Releaseon:
push:
branches:
- mainpermissions:
contents: read # for checkoutenv:
GOOGLE_CLIENT_ID: ${{secrets.GOOGLE_CLIENT_ID}}GOOGLE_CLIENT_SECRET: ${{secrets.GOOGLE_CLIENT_SECRET}}GOOGLE_REFRESH_TOKEN: ${{secrets.GOOGLE_REFRESH_TOKEN}}GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}jobs:
release:
name: Releaseruns-on: ubuntu-latestpermissions:
contents: write # to be able to publish a GitHub releaseissues: write # to be able to comment on released issuespull-requests: write # to be able to comment on released pull requestsid-token: write # to enable use of OIDC for npm provenancesteps:
- name: Checkoutuses: actions/checkout@v4with:
fetch-depth: 0
- name: Enable Corepack before setting up Noderun: corepack enable
- name: Setup Node.jsuses: actions/setup-node@v4with:
node-version: "20.x"cache: 'yarn'
- name: Install dependenciesrun: yarn install --immutable
- run: yarn build
- run: yarn test
- name: Verify the integrity of provenance attestations and registry signatures for installed dependenciesrun: yarn npm audit
- name: Releaserun: npx semantic-release
The text was updated successfully, but these errors were encountered:
A hopefully simple question about the refresh token. If I understand correctly, a refresh token can expire, but can be used to obtain a new refresh token. I'm concerned that when the refresh token expires, the deploy process will fail in my Github Action because the action isn't able to update the refresh token that I'm storing in my repo's secrets. Is this a valid concern? If yes, how should I handle this?
Issue
Your Environment
Github Action
semantic-release-chrome
version: 3.2.0node
version: v2.0npm
(oryarn
) version: 4.1.1Relevant code or config
The text was updated successfully, but these errors were encountered: