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 use of deprecated v3 actions/upload-artifact #413

Open
6 of 20 tasks
mikelittle opened this issue Feb 18, 2025 · 1 comment
Open
6 of 20 tasks

Upgrade use of deprecated v3 actions/upload-artifact #413

mikelittle opened this issue Feb 18, 2025 · 1 comment
Labels
bug Must have Must be done, high priority

Comments

@mikelittle
Copy link
Contributor

mikelittle commented Feb 18, 2025

Some GitHub actions for this repo are failing because the checks use v3 of the actions/uploadartifact module. This version has been deprecated for a while and reached end of life last month Deprecation notice: v3 of the artifact actions

Note: There are documented breaking changes, that may require adjustments to the actions.


Acceptance Criteria

  • The updated version is used in the tests
  • All tests continue to run successfully.

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
Copy link
Contributor Author

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

@mikelittle mikelittle added the Must have Must be done, high priority label Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Must have Must be done, high priority
Projects
None yet
Development

No branches or pull requests

1 participant