pig-tongzhi opened a new pull request, #69474:
URL: https://github.com/apache/doris/pull/69474

   ## 1. What problem was fixed
   
   Three more workflows in this repository still used `actions/checkout@v3`, 
which runs on a
   deprecated runtime inside GitHub Actions. This PR bumps them to `v4`:
   
   | Workflow | Occurrences |
   |---|---|
   | `.github/workflows/auto-cherry-pick.yml` | 1 |
   | `.github/workflows/be-ut-mac.yml` | 1 |
   | `.github/workflows/build-ui.yml` | 2 |
   
   ## 2. Which behaviors were modified
   
   None. Only the action version string changes:
   
   ```diff
   -        uses: actions/checkout@v3
   +        uses: actions/checkout@v4
   ```
   
   Previous behaviour: checkout with `v3`. New behaviour: checkout with `v4`, 
with all existing
   inputs unchanged — including `persist-credentials: false` in `be-ut-mac.yml` 
and `build-ui.yml`,
   which `v4` supports.
   
   ## 3. What features were added
   
   None — CI maintenance only.
   
   ## 4. Which code was refactored
   
   None. No Java/TS code, tests or build files are touched.
   
   ## 5. Which functions were optimized
   
   CI only: these checkout steps no longer depend on the deprecated runtime. 
Job runtime is unchanged.
   
   ## Scope / verification
   
   - 4 lines in 3 files.
   - Runners: `ubuntu-latest` and `macos-15` — both GitHub-hosted, so no 
self-hosted constraint.
   - This is a follow-up to #69319 (which updated `scope-label.yml`); files are 
disjoint, so the two
     PRs don't conflict.
   
   If you would prefer to keep `v3` pinned for a specific reason, I'm happy to 
close this. Thanks!
   


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to