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.

Sign up for GitHub

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

Jump to bottom

HCPCP-1615: upgrade hashicorp owned actions #96

Merged
merged 3 commits into from
May 24, 2024
Merged

HCPCP-1615: upgrade hashicorp owned actions #96

merged 3 commits into from
May 24, 2024

Conversation

WenInCode
Copy link
Contributor

@WenInCode WenInCode commented May 24, 2024 •
edited by jira bot
Loading

Changes proposed in this PR:

This upgrades any of the hashicorp owned actions that were giving warnings about Node 16.

Screenshot 2024-05-24 at 1 42 09 PM

HCPCP-1615

Checklist:

  • Tests added if applicable
  • CHANGELOG entry added or label 'pr/no-changelog' added to PR

    Run CHANGELOG_PR=<PR number> make changelog/new-entry for guidance
    in authoring a changelog entry, and commit the resulting file, which should
    have a name matching your PR number. Entries should use imperative present
    tense (e.g. Add support for...)

@WenInCode WenInCode added the pr/no-changelog Disable enforcement of changelog entry label May 24, 2024
@WenInCode WenInCode requested review from dadgar and a team as code owners May 24, 2024 19:44
@WenInCode WenInCode merged commit 3a304cc into main May 24, 2024
23 of 28 checks passed
@WenInCode WenInCode deleted the HCPCP-1615/upgrade-hashicorp-owned-actions branch May 24, 2024 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@natmegs natmegs natmegs approved these changes

@dadgar dadgar Awaiting requested review from dadgar

Assignees
No one assigned
Labels
pr/no-changelog Disable enforcement of changelog entry
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@WenInCode @natmegs