#10017 ci: Prevent cache poisoning attacks in th release workflow Pull request opened by edgarrmondragon Description As reported by zizmor:

error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
  --> .github/workflows/build.yml:42:7
   |
 3 | / on:
 4 | |   push:
 5 | |     branches-ignore:
 6 | |     - 'gh-readonly-queue/**'
...  |
18 | |   release:
19 | |     types: [published]
   | |______________________- generally used when publishing artifacts generated at runtime
...
42 |         uses: astral-sh/setup-uv@08807647e7069bb48b6ef5acd8ec9567f424441b # v8.1.0
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ enables caching by default
   |
   = note: audit confidence → Low
   = note: this finding has an auto-fix

error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
   --> .github/workflows/build.yml:112:7
    |
  3 | / on:
  4 | |   push:
  5 | |     branches-ignore:
  6 | |     - 'gh-readonly-queue/**'
...   |
 18 | |   release:
 19 | |     types: [published]
    | |______________________- generally used when publishing artifacts generated at runtime
...
112 |         uses: astral-sh/setup-uv@08807647e7069bb48b6ef5acd8ec9567f424441b # v8.1.0
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ enables caching by default
    |
    = note: audit confidence → Low
    = note: this finding has an auto-fix

Checklist • I have read the contribution guide Was generative AI tooling used to co-author this PR? • Yes (please specify the tool below) Related Issues • Closes #XXXX Summary by Sourcery Harden the GitHub Actions build workflow against cache poisoning by disabling caching in the uv setup steps. Bug Fixes: • Prevent potential cache poisoning in the release workflow by turning off uv action caching. CI: • Update the build workflow to configure astral-sh/setup-uv with caching disabled for all uses. meltano/meltano