Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update manifest.yml to use tag rather than sha #327

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

joshwlewis
Copy link
Member

The current iteration of https://s3.amazonaws.com/heroku_stacks_production/manifest.yml.signed currently includes entries with git shas like this:

git_ref: b4689bb306581b71b29701c55ecd9c6efb730d9c

Prior to #318, git tags were used instead. e.g.:

git_ref: v105

This PR updates the CI action to use git tags, as before.

@joshwlewis joshwlewis requested a review from a team as a code owner September 4, 2024 18:55
@@ -99,7 +99,7 @@ jobs:
path: /tmp/heroku-${{ matrix.stack-version }}*
- name: Upload heroku runtime images to staging
run: |
bin/upload-runtime-images.sh ${{ matrix.stack-version }} ${{ github.sha }}
bin/upload-runtime-images.sh ${{ matrix.stack-version }} ${{ github.ref_name }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The ctc-check job also uses github.sha (when iirc that used the tag before too). Should that be switched back to the tag too?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants