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

Upgrade NodeJS on Docker Actions #340

Open
19 tasks
mikelittle opened this issue Nov 22, 2024 · 1 comment
Open
19 tasks

Upgrade NodeJS on Docker Actions #340

mikelittle opened this issue Nov 22, 2024 · 1 comment
Labels

Comments

@mikelittle
Copy link
Contributor

mikelittle commented Nov 22, 2024

All the Docker actions run for this repo are giving warnings because Node 12 is out of date:

The following actions uses node12 which is deprecated and will be forced to run on node16: docker/metadata-action@v3, docker/setup-qemu-action@v1, docker/setup-buildx-action@v1, docker/login-action@v1. For more info:
https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

It looks like there are three actions: Build, Test, and Release

Reading the link from the warnings, it looks like they are now forced to run under Node 16. So we might as well update the configuration and remove the warnings.


Acceptance Criteria

  • The GH actions running on Tachyon run without warnings

For Altis Team Use

Ready for Work Checklist

Is this ticket ready to be worked on? See
the Play Book Definition of Ready

  • Is the title clear?
  • Is the description clear and detailed enough?
  • Are acceptance criteria listed?
  • Have any dependencies been identified? (Optional)
  • Have any documentation/playbook changes been identified? (Optional)
  • Is an estimate or time box assigned?
  • Is a priority label assigned?
  • Is this ticket added to a milestone?
  • Is this ticket added to an epic? (Optional)

Completion Checklist

Is this ticket done? See
the Play Book Definition of Done

  • Has the acceptance criteria been met?
  • Is the documentation updated (including README)?
  • Do any code/documentation changes meet project standards?
  • Are automatic tests in place to verify the fix or new functionality?
    • Or are manual tests documented (at least on this ticket)?
  • Are any Playbook/Handbook pages updated?
  • Has a new module release (patch/minor) been created/scheduled?
  • Have the appropriate backport labels been added to the PR?
  • Is there a roll-out (and roll-back) plan if required?
@mikelittle mikelittle added the bug label Nov 22, 2024
@wisyhambolu
Copy link
Contributor

Hey team! Please add your planning poker estimate with Zenhub @ferschubert-hm @mikelittle @owaincuvelier

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

No branches or pull requests

2 participants