chore: Set permissions for GitHub actions Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much. - Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs [Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/) Signed-off-by: naveen <172697+naveensrinivasan@users.noreply.github.com>
34 lines
No EOL
943 B
YAML
34 lines
No EOL
943 B
YAML
name: Generate Semantic Release
|
|
on:
|
|
push:
|
|
branches:
|
|
- version-14-beta
|
|
permissions:
|
|
contents: read
|
|
|
|
jobs:
|
|
release:
|
|
name: Release
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Checkout Entire Repository
|
|
uses: actions/checkout@v2
|
|
with:
|
|
fetch-depth: 0
|
|
persist-credentials: false
|
|
- name: Setup Node.js v14
|
|
uses: actions/setup-node@v2
|
|
with:
|
|
node-version: 14
|
|
- name: Setup dependencies
|
|
run: |
|
|
npm install @semantic-release/git @semantic-release/exec --no-save
|
|
- name: Create Release
|
|
env:
|
|
GH_TOKEN: ${{ secrets.RELEASE_TOKEN }}
|
|
GITHUB_TOKEN: ${{ secrets.RELEASE_TOKEN }}
|
|
GIT_AUTHOR_NAME: "Frappe PR Bot"
|
|
GIT_AUTHOR_EMAIL: "developers@frappe.io"
|
|
GIT_COMMITTER_NAME: "Frappe PR Bot"
|
|
GIT_COMMITTER_EMAIL: "developers@frappe.io"
|
|
run: npx semantic-release |