Bump actions/upload-artifact off v4 (Node 20) before Sept 16, 2026

未关闭 适合新手
  • 哪里不对？
#1,089 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
64/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
冷清
技术栈
github-actions, yaml
领域
ci-cd

调研方向

阅读.github/workflows/ci-build.yml并检查链接的actions/upload-artifact#806 issue，以确认 v7 回归问题是否已解决。除非已确认 v7 安全，否则将 artifact action 更新到 v6，并审查提到的 actions 以及有关 Node 20 弃用的 CI 警告。完成标准是 workflow 不再依赖使用 Node 20 的 actions，且 CI 通过。

由索引模型根据 Issue 内容生成。

描述

infrastructure

Background

PR #1088 pinned actions/upload-artifact to v4.6.2 (in .github/workflows/ci-build.yml) to avoid an intermittent silent-failure regression on v7 (see actions/upload-artifact#806).

v4 runs on Node.js 20. GitHub is sunsetting Node 20 on the Actions runner:

  • June 2, 2026: Node 24 becomes the default runtime. v4 still works but emits a deprecation warning on every run.
  • September 16, 2026: Node 20 is removed. v4 will stop working unless ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true is set on the runner / workflow (foot-gun; don't do this).

Source: GitHub Actions runner deprecation notice (visible as a warning annotation on every run after June 2):

Node.js 20 actions are deprecated... Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026.

What to do before September 16, 2026

Pick one:

  1. Upgrade to actions/[email protected] (Node 24, pre-ESM, no known silent-failure regressions). Single-file change.
  2. Upgrade to @v7.x if the silent-failure regression has been fixed by then. Check actions/upload-artifact#806 and similar issues before going to v7.

Recommend option 1 unless v7 issues are resolved.

Other Node-20 actions to audit at the same time

While we're at it, check these for the same Node 20 / Node 24 transition:

  • dotnet/[email protected] (already flagged with the same deprecation warning on current builds)
  • actions/[email protected] (verify which Node version it runs on)
  • Any others surfaced by the deprecation warnings in the next CI run.

Don't lose track

This issue must be resolved before September 16, 2026 or PR CI breaks.

主要语言
C#
星标
1.9k
派生
194
平均合并
12 分钟
30 天内合并 PR
1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

reactivemarbles/DynamicData 的其他 Issue

查看 reactivemarbles/DynamicData 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。