takayoshi-makabe opened a new pull request, #4025:
URL: https://github.com/apache/iceberg-python/pull/4025

   # Rationale for this change
   
   asf-allowlist-check currently fails on every pull request in this 
repository, unrelated to the changes in the PR:
   
   astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39 is not on the 
ASF allowlist
   
   The pinned ref (v8.2.0, added in #3510) carried expires_at: 2026-09-27 and 
was dropped by 
apache/infrastructure-actions@0e7dc9e9f5465ef35bac08b250a9fd9398f8f46a ("Remove 
Expired Refs") at 2026-09-27 02:30 UTC. The check fetches actions.yml at run 
time, so runs before that commit passed and every run after it fails.
   
   This is the same failure previous pin (v7.3.1) expired.
   
   v10.2.0 (c18668ad3cf93e7) is the only astral-sh/setup-uv entrt an 
expires_at, so it maximises the time unti the SHA matches the v10.2.0 tag.
   
   Two upstream breaking changes are crossed, neither of which breaks CI here:
   
   - v9.0.0 changed the prune-cache default to false. This repository does not 
set it, so caches will grow; upstream made this change deliberately to reduce 
load on PyPI.
   - v10.0.0 disables caching under enable-cache: auto for release, tag push, 
pull_request_target and workflow_run events. 9 of the 14 call sites set 
enable-cache explicitly. Of the 5 that rely on the default, only 
svn-build-artifacts.yml and pypi-build-artifacts.yml are affected, and only 
when called from python-release.yml on a tag push — where the caller already 
sets enable-cache: false.
   
   ## Are these changes tested?
   
   ## Are there any user-facing changes?
   
   <!-- In the case of user-facing changes, please add the changelog label. -->
   


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