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

📋 [TASK] - Investigate upload-artifacts Version Migration #807

Closed
3 tasks done
lizzcondrey opened this issue Apr 22, 2024 · 1 comment
Closed
3 tasks done

📋 [TASK] - Investigate upload-artifacts Version Migration #807

lizzcondrey opened this issue Apr 22, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request research An issue that needs to be researched more
Milestone

Comments

@lizzcondrey
Copy link
Collaborator

lizzcondrey commented Apr 22, 2024

Parent Feature

#799

Task Description

As an AaC CI/CD Developer, I need to investigate the version migration of the upload-artifacts action, so that I do not cause pipeline breakage by migrating major versions.

Acceptance Criteria

  • Spend no more than two days researching the migration impacts of changing from v3 to v4 for upload-artifacts action in pipelines
  • Identify useful resources for generating a solution for the migration.
  • Document the potential solution(s) for implementing the migration.

Unresolved questions

No response

@lizzcondrey lizzcondrey added the enhancement New feature or request label Apr 22, 2024
@lizzcondrey lizzcondrey added this to the 24.2.1 milestone Apr 22, 2024
@lizzcondrey lizzcondrey added the research An issue that needs to be researched more label Apr 22, 2024
@lizzcondrey lizzcondrey self-assigned this May 21, 2024
@lizzcondrey
Copy link
Collaborator Author

lizzcondrey commented May 28, 2024

Upload & Download @v4 action breakage
upload-artifact/docs/MIGRATION.md at main · actions/upload-artifact (github.com)
upload-artifact/README.md at main · actions/upload-artifact (github.com)

We are migrating from v3 to v4, so we are able to hold on the migration till next iteration like originally thought. It's v2 that is deprecated and stopping support June 30th. November 30th is when v3 will be deprecated, which is just after the end of the next iteration. So, we are good to continue with the plan of handling all action migrations next iteration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request research An issue that needs to be researched more
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant