1. actions/download-artifiact 버전 오류 발생
Error: This request has been automatically failed because it uses a deprecated version of `actions/download-artifact: v3`. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
actions/download-artifact: v3 를 더 이상 지원하지 않는다는 오류 발생
Deprecation notice: v3 of the artifact actions · GitHub Changelog
Starting January 30th, 2025, GitHub Actions customers will no longer be able to use v3 of actions/upload-artifact or actions/download-artifact. Customers should update workflows to begin using v4 of the artifact…
github.blog
Starting January 30th, 2025, GitHub Actions customers will no longer be able to use v3 of actions/upload-artifact or actions/download-artifact. Customers should update workflows to begin using v4 of the artifact actions as soon as possible. While v4 of the artifact actions improves upload and download speeds by up to 98% and includes several new features, there are key differences from previous versions that may require updates to your workflows. Please see the documentation in the project repositories for guidance on how to migrate your workflows.
The deprecation of v3 will be similar to the previously announced v1 and v2 deprecation plans, which is scheduled to take place on June 30, 2024. Version tags will not be removed from the project repositories, however, attempting to use a version of the actions after the deprecation date will result in a workflow failure. Artifacts within their retention period will remain accessible from the UI or REST API regardless of the version used to upload. This deprecation will not impact any existing versions of GitHub Enterprise Server being used by customers.
This announcement will also be added to actions/upload-artifact and actions/download-artifact. Please visit the documentation to learn more about storing workflow data as artifacts in Actions.
공식문서를 살펴보면 '2025년 1월 30일부터 GitHub Actions 사용자는 actions/upload-artifact 또는 actions/download-artifact의 v3 버전을 더 이상 사용할 수 없습니다. 사용자는 워크플로우를 가능한 한 빨리 artifact 액션의 v4 버전을 사용하도록 업데이트해야 합니다.' 라고 한다.
즉, 2025년 1월 30일 부터 actions/download-artifact: v3 대신 actions/download-artifact: v4 를 사용하여야 한다
👉 actions/download-artifact: v4 로 버전 변경
2. Artifact not found for name : build-libs 오류 발생
Error: Unable to download artifact(s): Artifact not found for name: build-libs
Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact.
For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
build-libs 라는 이름의 아티팩트를 다운로드 할 수 없다는 오류 발생
아티팩트가 만료되지 않았는지 확인하고, 호환되는 버전의 toolkit/upload-artifact 를 사용하여 업로드 했는지 확인하라고 한다.
toolkit/packages/artifact/docs/faq.md at main · actions/toolkit
The GitHub ToolKit for developing GitHub Actions. Contribute to actions/toolkit development by creating an account on GitHub.
github.com
Which versions of the artifacts packages are compatible?
actions/upload-artifact and actions/download-artifact, leverage GitHub Actions toolkit and are typically used together to upload and download artifacts in your workflows.
Use matching versions of
upload-artifact download-artifact toolkit v4 v4 v2 < v3 < v3 < v1 actions/upload-artifactandactions/download-artifactto ensure compatibility.
In your GitHub Actions workflow YAML file, you specify the version of the actions you want to use.
For example:
uses: actions/upload-artifact@v4 # ... uses: actions/download-artifact@v4 # ...
Release Notes: Check the release notes for each repository to see if there are any specific notes about compatibility or changes in behavior.
공식문서에서 '호환성을 보장하려면 actions/upload-artifact와 actions/download-artifact의 버전을 일치시켜 사용하세요.' 라고 한다
즉, actions/upoload-artifact@v4, actions/download-artifact@v4, toolkit(v2) 세 가지는 모두 버전이 일치 해야 호환이 된다.
👉 앞에서 download-artifact 버전을 4로 변경하였으니, actions/upoload-artifact@v4 로 변경
3. ECS 작업 정의에 포함될 수 없는 키 enableFaultInjection 오류
Error: Failed to register task definition in ECS: Unexpected key 'enableFaultInjection' found in params
Error: Unexpected key 'enableFaultInjection' found in params
매개변수에서 예상하지 못한 키 enableFaultInjection이 발견되어, ECS에서 작업 정의를 등록하는 데 실패했다는 오류 발생
Unexpected key 'enableFaultInjection' found in params
suddenly,not able to deploy the task definition. It has "enableFaultInjection":false as default value but failing the deployment with the following error: Error: Failed to register task definition...
repost.aws
You are likely using v1 of the ecs-deploy-task-defintion GitHub action, you should be using v2 as this was fixed there yesterday as well.
- name: Deploy Amazon ECS task definition uses: aws-actions/amazon-ecs-deploy-task-definition@v2 with: task-definition: task-definition.json
공식문서 에서 '당신은 아마도 ecs-deploy-task-definition GitHub 액션의 v1을 사용하고 있는 것 같습니다. 어제 그 문제가 v2에서 수정되었기 때문에 v2를 사용해야 합니다.' 라고 한다.
v1에서 발생한 문제는 v2에서 해결되었으니, aws-actions/amazon-ecs-deploy-task-definition@v2를 사용해야 한다
👉 aws-actions/amazon-ecs-deploy-task-definition@v2 로 변경
( aws-actions/amazon-ecs-render-task-definition@v1 이거랑 헷갈려서 잘 못 바꾸지 않도록 조심)
'TIL' 카테고리의 다른 글
| [25.04.02] TIL - 웹 서버와 웹 어플리케이션 서버의 차이? (0) | 2025.04.03 |
|---|---|
| [25.03.30] TIL - 변수 네이밍 (0) | 2025.03.30 |
| [25.03.29] TIL - 자바 인스턴스 변수 생명주기 확인하기 (0) | 2025.03.30 |
| [25.03.28] TIL - 중앙처리장치, 주기억장치, 보조기억장치 란? (0) | 2025.03.28 |
| [25.03.13] TIL - MSA 구조에서의 DB 구성 (0) | 2025.03.13 |