TL;DR
- Disabled pull requests from being created using the input variable
skip-github-pull-request: true.
- Action fails to do anything to the main branch.
- Action fails to create a release.
It's entirely possible this is desired behaviour, but the action isn't creating a release either despite the explicit skip-github-release: false.
If there's no scope for this project to skip the pull requests but also keep making releases/pushing tags please close this issue.
Expected behavior
Expected the action to:
- Clone the repository
- Do the version bumping based on the last merged pull request message prefix
- Push the tag back to the main branch without needing the release pull request phase
Additionally, but optionally, creating the github release at the same time if desired.
Observed behavior
The action is triggered successfully on PR being merged but no mutation of the repository is observed.
Action YAML
on:
push:
branches:
- main
permissions:
contents: write
pull-requests: write
name: release-please
jobs:
release-please:
runs-on: ubuntu-latest
steps:
- uses: google-github-actions/release-please-action@v4
id: release
with:
token: ${{ secrets.RELEASE_PLEASE_TOKEN }}
release-type: simple
skip-github-pull-request: true
skip-github-release: falseLog output
Run google-github-actions/release-please-action@v4
✔ Looking for latest release on branch: main with prefix:
❯ Fetching merge commits on branch main with cursor: undefined
❯ Found latest release pull request: 26 version: 0.0.9
❯ Fetching releases with cursor undefined
❯ found release for Version {
major: 0,
minor: 0,
patch: 9,
preRelease: undefined,
build: undefined
}
❯ found release for Version {
major: 0,
minor: 0,
patch: 8,
preRelease: undefined,
build: undefined
}
❯ SHA not found in recent commits to branch main, skipping
❯ found release for Version {
major: 0,
minor: 0,
patch: 7,
preRelease: undefined,
build: undefined
}
❯ SHA not found in recent commits to branch main, skipping
❯ found release for Version {
major: 0,
minor: 0,
patch: 6,
preRelease: undefined,
build: undefined
}
❯ SHA not found in recent commits to branch main, skipping
❯ found release for Version {
major: 0,
minor: 0,
patch: 5,
preRelease: undefined,
build: undefined
}
❯ SHA not found in recent commits to branch main, skipping
❯ found release for Version {
major: 0,
minor: 0,
patch: 4,
preRelease: undefined,
build: undefined
}
❯ SHA not found in recent commits to branch main, skipping
❯ found release for Version {
major: 0,
minor: 0,
patch: 3,
preRelease: undefined,
build: undefined
}
❯ SHA not found in recent commits to branch main, skipping
❯ found release for Version {
major: 0,
minor: 0,
patch: 2,
preRelease: undefined,
build: undefined
}
❯ SHA not found in recent commits to branch main, skipping
❯ found release for Version {
major: 0,
minor: 0,
patch: 1,
preRelease: undefined,
build: undefined
}
❯ SHA not found in recent commits to branch main, skipping
❯ found 2 possible releases. [
Version {
major: 0,
minor: 0,
patch: 9,
preRelease: undefined,
build: undefined
},
Version {
major: 0,
minor: 0,
patch: 9,
preRelease: undefined,
build: undefined
}
]
✔ Building releases
✔ Building strategies by path
❯ .: simple
Additional information
Previous builds have been success with skip-github-pull-request: false flag being left as default, to explain why there's values up to v0.0.9.
I am using a PAT to avoid the github limitation of not triggering subsequent jobs using the default GITHUB_TOKEN to write back to the repository.
The PAT has full repository read/write, and package write scopes.
This is an attempt to remove the release PR part of the workflow but retain the other part of the functionality, namely creating tags automatically on commit message prefixes being pushed to main.
TL;DR
skip-github-pull-request: true.It's entirely possible this is desired behaviour, but the action isn't creating a release either despite the explicit
skip-github-release: false.If there's no scope for this project to skip the pull requests but also keep making releases/pushing tags please close this issue.
Expected behavior
Expected the action to:
Additionally, but optionally, creating the github release at the same time if desired.
Observed behavior
The action is triggered successfully on PR being merged but no mutation of the repository is observed.
Action YAML
Log output
Additional information
Previous builds have been success with
skip-github-pull-request: falseflag being left as default, to explain why there's values up to v0.0.9.I am using a PAT to avoid the github limitation of not triggering subsequent jobs using the default
GITHUB_TOKENto write back to the repository.The PAT has full repository read/write, and package write scopes.
This is an attempt to remove the release PR part of the workflow but retain the other part of the functionality, namely creating tags automatically on commit message prefixes being pushed to main.