Skip to content

Commit

Permalink
Use GITHUB_REF_NAME instead of GITHUB_REF
Browse files Browse the repository at this point in the history
Previously the workflow was using GITHUB_REF which is refs/heads/tag-name instead of tag-name. This has been fixed.
  • Loading branch information
hmstepanek authored Jan 30, 2025
1 parent db9f7c8 commit 118fbda
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions .github/workflows/lambda_release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,9 @@ jobs:

- name: Create release tags for Lambda and K8s Init Containers
run: |
RELEASE_TITLE="New Relic Ruby Agent ${GITHUB_REF}.0"
RELEASE_TAG="${GITHUB_REF}.0_ruby"
RELEASE_NOTES="Automated release for [Ruby Agent ${GITHUB_REF}](https://github.com/newrelic/newrelic-ruby-agent/releases/tag/${GITHUB_REF})"
RELEASE_TITLE="New Relic Ruby Agent ${GITHUB_REF_NAME}.0"
RELEASE_TAG="${GITHUB_REF_NAME}.0_ruby"
RELEASE_NOTES="Automated release for [Ruby Agent ${GITHUB_REF_NAME}](https://github.com/newrelic/newrelic-ruby-agent/releases/tag/${GITHUB_REF_NAME})"
gh auth login --with-token <<< $GH_RELEASE_TOKEN
echo "newrelic/newrelic-lambda-layers - Releasing ${RELEASE_TITLE} with tag ${RELEASE_TAG}"
gh release create "${RELEASE_TAG}" --title=${RELEASE_TITLE} --repo=newrelic/newrelic-lambda-layers --notes=${RELEASE_NOTES}
Expand Down

0 comments on commit 118fbda

Please sign in to comment.