pig-tongzhi opened a new pull request, #20411:
URL: https://github.com/apache/hudi/pull/20411
### Describe the issue this Pull Request addresses
Two workflows in this repository still pin `actions/checkout@v2`, which runs
on the deprecated
Node 12 runtime inside GitHub Actions:
- `.github/workflows/azure_ci_check.yml` (the "Azure CI" workflow)
- `.github/workflows/scheduled_workflow.yml` (the "Scheduled Workflow")
`v2` has been superseded twice (`v3` → `v4`), and `v4` is the current major
version. Since these two
files are the only remaining `checkout@v2` usages in `.github/workflows`,
this keeps the whole
repository consistent.
### Summary and Changelog
- Bump `actions/checkout` from `v2` to `v4` in `azure_ci_check.yml` (1 line)
and
`scheduled_workflow.yml` (1 line).
- No other change: no steps added/removed, no `with:` inputs, no env, no job
logic touched.
- Both jobs run on `ubuntu-latest` (GitHub-hosted), so `v4`'s runner
requirement (≥ 2.308) is met.
Changelog: `actions/checkout` `v2` → `v4` in two workflows (2 lines total).
### Impact
None for users. CI only — the checkout step behaves the same for these two
plain checkouts (no
`sparse-checkout`, no `submodules`, no `persist-credentials` inputs are
used).
### Risk Level
**none**
Reasoning: the diff is two version tags. The action's inputs and outputs
used by these workflows are
identical between `v2` and `v4`, and both jobs run on GitHub-hosted runners.
### Documentation Update
none — no new config, feature or user-facing behaviour.
### Contributor's checklist
- [x] Read through [contributor's
guide](https://hudi.apache.org/contribute/how-to-contribute)
- [x] Enough context is provided in the sections above
- [x] Adequate tests were added if applicable — not applicable,
CI-version-only change
<!-- rebased onto master 62bae026d5 -->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]