googleapis / googleapis/release-please-action
Add version outputs for created PRs
- Dominant language
- TypeScript
- Stars
- 2.5k
- Forks
- 327
- PR merge metrics
- No merged PRs in 30d
Description
### TL;DR
I'm trying to use the action outputs in a slack notification message but for some reason they are blank
### Expected behavior
`steps.release.outputs.pr` has the value of the created PR
### Observed behavior
Value is empty
### Action YAML
```yaml
on:
push:
branches:
- master
name: release-please
env:
GITHUB_TOKEN: ${{ secrets.SCOPED_TOKEN }}
jobs:
release-please:
if: ${{ !contains(github.event.pull_request.labels.*.name, 'autorelease') }}
runs-on: ubuntu-latest
steps:
- name: Create Release PR
uses: google-github-actions/release-please-action@v3
id: release
with:
token: ${{ secrets.SCOPED_TOKEN }}
release-type: node
package-name: "MY_PACKAGE_NAME"
labels: autorelease
- name: Slack Notification
uses: rtCamp/action-slack-notify@v2
env:
SLACK_WEBHOOK: ${{ secrets.SLACK_WEBHOOK }}
SLACK_CHANNEL: SLACK_CHANNEL
SLACK_MESSAGE: 'Release PR has been created for version : ${{ steps.release.outputs.major }}.${{ steps.release.outputs.minor }}.${{ steps.release.outputs.patch }}. See it here: https://github.com/OWNER/REPO/pull/${{ steps.release.outputs.pr_number }}'
MSG_MINIMAL: true
```
### Log output
```text
28s
Run google-github-actions/release-please-action@v3
✔ Looking for latest release on branch: master with prefix: PREFIX
❯ Fetching merge commits on branch master with cursor: undefined
❯ Found latest release pull request: 506 version: 11.4.0
❯ Fetching releases with cursor undefined
✔ Building releases
✔ Building strategies by path
❯ .: node
✔ Looking for latest release on branch: master with prefix: PREFIX
❯ Fetching merge commits on branch master with cursor: undefined
❯ Found latest release pull request: 506 version: 11.4.0
❯ Fetching releases with cursor undefined
✔ Building pull requests
✔ Building strategies by path
❯ .: node
✔ Collecting release commit SHAs
❯ release search depth: 400
❯ Fetching releases with cursor undefined
❯ Found release for path ., v11.4.0
❯ release for path: ., version: 11.4.0, sha: SHA
✔ Collecting commits since all latest releases
❯ commit search depth: 500
✔ Splitting 7 commits by path
✔ Building candidate release pull request for path: .
❯ type: node
❯ targetBranch: master
❯ commit could not be parsed: feb6ca287d8c960881e5eea49477396e2a311416 remove comment
❯ commits: 6
✔ Considering: 6 commits
❯ component:
❯ pull request title pattern: undefined
✔ Looking for open release pull requests
✔ found 0 open release pull requests.
✔ Looking for snoozed release pull requests
✔ found 0 snoozed release pull requests.
❯ Fetching package-lock.json from branch master
✔ updating from 11.4.0 to 11.4.1
❯ Fetching npm-shrinkwrap.json from branch master
⚠ file npm-shrinkwrap.json did not exist
⚠ file samples/package.json did not exist
❯ Fetching samples/package.json from branch master
❯ Fetching CHANGELOG.md from branch master
❯ Fetching package.json from branch master
✔ updating from 11.4.0 to 11.4.1
❯ Fetching .release-please-manifest.json from branch master
⚠ file .release-please-manifest.json did not exist
✔ Starting GitHub PR workflow...
✔ Successfully found branch HEAD sha "1b92cc5bed65da52de8ce9157bf96e405e56d2f3".
✔ Skipping branch creation step...
✔ Got the latest commit tree
✔ Successfully created a tree with the desired changes with SHA 8e0f0a5dea23862bab2ff3902ae2d4c233de500d
✔ Successfully created commit. See commit at https://api.github.com/
✔ Updating reference to fb76150d735a729cb2373889d4be2d9584e9461c
✔ Successfully updated reference fb76150d735a729cb2373889d4be2d9584e9461c
✔ Successfully opened pull request available at url:
✔ Successfully opened pull request: 510.
✔ Successfully added labels autorelease to issue: 510
1s
Run rtCamp/action-slack-notify@v2
env:
GITHUB_TOKEN: ***
SLACK_WEBHOOK: ***
SLACK_CHANNEL: ***
SLACK_COLOR: good
SLACK_MESSAGE: Release PR has been created for version : ... See it here: https://github.com/OWNER/REPO/pull/
MSG_MINIMAL: true
```
### Additional information
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.