CritasWang opened a new pull request, #44:
URL: https://github.com/apache/tsfile-viewer/pull/44

   ## Summary
   
   Follow-up to #39 (and #36) based on a pass over 
https://infra.apache.org/github-actions-policy.html and the pages it links to.
   
   The policy requires automatic dependency management for the `github-actions` 
ecosystem and points at https://infra.apache.org/dependabot.html for how to 
configure it, *including grouping security updates so that a burst of 
advisories does not turn into a burst of CI runs*. The Dependabot guidance also 
recommends a cooldown period, and `apache/infrastructure-actions` recommends 
the same for ASF projects.
   
   The current configuration already shows why: bumping the four pinned actions 
produced four pull requests (#40–#43), each triggering its own workflow run.
   
   This PR:
   
   - groups the routine version bumps into one pull request (`applies-to: 
version-updates`)
   - groups the security updates into one pull request (`applies-to: 
security-updates`)
   - adds a 4-day cooldown so a release has time to settle before it is proposed
   
   Only `.github/dependabot.yml` is touched — no workflow file.
   
   ## Why this matters right now
   
   `dorny/test-reporter@3eeb9fc8… # v1` is not on the ASF organization-wide 
allow list, so every run of `tsfile-model-tests.yml` fails at startup with no 
jobs at all (on `main` as well). External actions are blocked by default in 
`apache/*` repositories; the allow list only approves 
`dorny/test-reporter@a43b3a5f…` (v3.0.0), which is exactly what #43 proposes, 
so #43 is the one that makes CI usable again.
   
   Refs https://infra.apache.org/github-actions-policy.html (External actions), 
https://infra.apache.org/dependabot.html, 
https://github.com/apache/infrastructure-actions
   


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

Reply via email to