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

Remove deprecation warnings from Github Actions #959

Merged
merged 5 commits into from
Jan 2, 2023

Conversation

rebeccabilbro
Copy link
Collaborator

Scope of changes

This PR attempts to address the deprecation warnings related to the set-output workflow in Github Actions, which I believe Ensign is using to determine the commit and branch is being shown in the front end. I've used the instructions posted by Github here. Fixes SC-10218

Type of change

  • bug fix
  • new feature
  • documentation
  • other (resolve deprecation warning in GH Action)

Acceptance criteria

If this works, the deprecations warnings in Github Actions should go away (at least the ones related to set-output 😄 )

Author checklist

  • I have manually tested the change and/or added automation in the form of unit tests or integration tests
  • I have updated the dependencies list
  • I have recompiled and included new protocol buffers to reflect changes I made
  • I have added new test fixtures as needed to support added tests
  • Check this box if a reviewer can merge this pull request after approval (leave it unchecked if you want to do it yourself)
  • I have moved the associated Shortcut story to "Ready for Review"

Reviewer(s) checklist

  • Any new user-facing content that has been added for this PR has been QA'ed to ensure correct grammar, spelling, and understandability.

echo "::set-output name=tag::${GITHUB_REF#refs/*/}"
echo "::set-output name=revision::$(git rev-parse --short HEAD)"
echo "tag=${GITHUB_REF#refs/*/}" >> $GITHUB_OUTPUT
echo "revision=$(git rev-parse --short HEAD)" >> $GITHUB_OUTPUT
Copy link
Collaborator

Choose a reason for hiding this comment

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

Are we missing something? I'm still seeing some set-output warnings in the CI: https://github.com/trisacrypto/directory/actions/runs/3680285547

Copy link
Collaborator Author

@rebeccabilbro rebeccabilbro Dec 12, 2022

Choose a reason for hiding this comment

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

It looks like those deprecation warnings are bubbling up from some of our dependencies; once they have updated their actions as we have done in this PR, they should hopefully all go away. It might require us to update some of the action versions pinned in our yaml files.

Copy link
Collaborator

@pdeziel pdeziel left a comment

Choose a reason for hiding this comment

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

LGTM!

@rebeccabilbro rebeccabilbro merged commit c2aaa39 into main Jan 2, 2023
@rebeccabilbro rebeccabilbro deleted the deprecation-warnings branch January 2, 2023 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants