Files
awesome-cordova-plugins/.github/workflows/release-please.yml
T
Daniel Sogl ef358238c2 ci: update release-please-action to v5
The only breaking change in v5.0.0 is the move to the node 24 runtime; inputs,
outputs and the manifest/config format are unchanged. Kept as its own commit
since this action drives the release flow and is the one worth reverting alone
if anything misbehaves.
2026-07-27 21:35:14 +02:00

69 lines
1.9 KiB
YAML

name: Release Please
on:
push:
branches: [main]
workflow_dispatch:
permissions:
contents: write
pull-requests: write
issues: write
id-token: write
jobs:
release-please:
runs-on: ubuntu-latest
outputs:
release_created: ${{ steps.release.outputs.release_created }}
tag_name: ${{ steps.release.outputs.tag_name }}
version: ${{ steps.release.outputs.version }}
steps:
- name: Run Release Please
id: release
uses: googleapis/release-please-action@v5.0.0
with:
token: ${{ secrets.GITHUB_TOKEN }}
config-file: release-please-config.json
manifest-file: .release-please-manifest.json
# npm trusted publishing validates the OIDC claim of the *entry point* workflow,
# not the one that runs `npm publish`. Keep this job inline — a reusable workflow
# here breaks the trust check. See https://github.com/npm/documentation/issues/1755
publish:
needs: release-please
if: ${{ needs.release-please.outputs.release_created }}
runs-on: ubuntu-latest
permissions:
contents: read
id-token: write
steps:
- uses: actions/checkout@v7.0.1
- name: Setup Node.js
uses: actions/setup-node@v7.0.0
with:
# node 24 bundles npm 11.16, over the >= 11.5.1 that trusted publishing needs
node-version: 24
cache: npm
registry-url: https://registry.npmjs.org
- name: Install dependencies
run: npm ci
- name: Lint
run: npm run lint -- --quiet
- name: Test
run: npm test
- name: Build
run: npm run build
- name: Publish to npm
env:
# fallback for packages without a trusted publisher yet (e.g. brand new plugins).
# OIDC takes precedence whenever the package has one configured.
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
run: npm run npmpub