Skip to content

Update github-actions (major) - #781

Open
renovate[bot] wants to merge 1 commit into
2.0.xfrom
renovate/major-github-actions
Open

Update github-actions (major)#781
renovate[bot] wants to merge 1 commit into
2.0.xfrom
renovate/major-github-actions

Conversation

@renovate

@renovate renovate Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
astral-sh/setup-uv action major v8.3.2v10.0.1
metcalfc/changelog-generator action major v4.8.0v5.0.1

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

astral-sh/setup-uv (astral-sh/setup-uv)

v10.0.1: 🌈 Tolerate transient manifest timeouts

Compare Source

Changes

Thank you @​arguile- for making this action more resilient.

🐛 Bug fixes
🧰 Maintenance
📚 Documentation

v10.0.0: 🌈 Disable automatic caching for sensitive events and new QOL features

Compare Source

Changes

Another breaking release, directly after v9.0.0 but we think the added security justifies that.

Extra security by default

If you use the default enable-cache: auto this will now DISABLE THE CACHE to protect against cache poisoning for the following events:

  • pull_request_target
  • workflow_run
  • release

You can read the full reasoning in #​984

version: latest-known
- name: Install the latest version of uv known to setup-uv
  uses: astral-sh/setup-uv@v10.0.0
  with:
    version: "latest-known"

This will now install the latest version with a checksum that is known by this action. The known uv checksums are automatically updated but will take a release of this action to take effect. You won't be always using the latest & greatest but you will have an extra level of security.

Read python version from .tool-versions
- name: Install uv based on the version defined in .tool-versions and also set python
  uses: astral-sh/setup-uv@v10.0.0
  with:
    version-file: "pyproject.toml"

Will now also set the python version if it is defined in .tool-versions. You can read the details in the docs

🚨 Breaking changes
🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates

v9.0.0

Compare Source

metcalfc/changelog-generator (metcalfc/changelog-generator)

v5.0.1

Compare Source

  • 031a640 - 5.0.1
  • 122a6c2 - Base the changelog on the previous release of the same line, and assert it (#​479)
  • 0bee5ad - fix: return the modified changelog as a real multiline output (#​478)

v5.0.0

Compare Source

Breaking change: commit subjects render as literal text

Every changelog line now wraps the commit subject in an inline-code span.

before:  - [f723555](.../commit/f723555) - build(deps-dev): bump @vercel/ncc to 0.45.0 (#​470)
after:   - [f723555](.../commit/f723555) - ` build(deps-dev): bump @vercel/ncc to 0.45.0 (#​470) `

A commit subject is untrusted input. Anyone whose pull request you merge
chooses that text, and this action pastes it directly into your release notes.
Rendered as active Markdown, a subject could contribute links, images,
@mentions, issue references, raw HTML, or additional changelog entries to a
release it had no business editing. Rendering it as literal text closes that
off.

What this costs you. Subjects render monospace, and #123, GH-123, bare
commit SHAs, and :emoji: inside a subject no longer autolink. Because
GitHub's squash merge appends (#​123) to the subject by default, most lines
in a typical repository lose that link. The generated commit link at the start
of each line is unaffected. Control characters, line and paragraph separators,
and bidirectional-control characters are replaced with spaces, so a subject can
never span more than its own line.

No inputs or outputs changed, and the No Changes. sentinel is unchanged.

Staying on the previous format

v4.9.0
carries every security and dependency fix in this release
-- including undici
7.29.0, which closes 12 advisories -- with the v4 output format untouched. Pin
metcalfc/changelog-generator@v4 to stay there. The v4 tag will keep moving
on the maintenance line.

What is in this release

Relative to v4.9.0, v5.0.0 adds only the escaping change. Both releases share
everything else:

  • Render changelog subjects as literal text (#​475) -- v5 only
  • Keep release tag names out of shell source (#​473)
  • Verify release bundle before attestation (#​474)
  • Bound the dependency overrides and clear the undici advisories (#​476)
  • Stop bump:workflow rewriting pinned actions' provenance comments (#​477)
  • Bump @vercel/ncc (#​470), eslint (#​472), globals (#​471), codeql-action (#​469)

Full history: v4.8.0...v5.0.0

v5

Compare Source

v4.9.1

Compare Source

Patch release for the v4 line

Documentation and CI only. dist/ is byte-identical to
v4.9.0
,
so there is no functional change for consumers; this release exists so the v4
tag points at a commit whose docs are correct.

  • Return the modified changelog as a real multiline output (#​478)

The README's "Simple output modifications" recipe percent-encoded newlines as
%0A, which the long-removed ::set-output command decoded. $GITHUB_OUTPUT
does not, so anyone who copied that snippet got a single line with literal
%0A in it. It now uses the heredoc form, with a random delimiter because the
value is built from commit subjects.

The changelog output format remains unchanged from v4.8.0. See
v5.0.0
for the breaking change that renders commit subjects as literal text.

v4.9.0

Compare Source

Maintenance release for the v4 line

Security and dependency fixes only. The changelog output format is unchanged
from v4.8.0
-- verified byte-identical -- so tracking @v4 is safe.

  • undici 7.29.0, closing all 12 open advisories (4 high)
  • release-workflow hardening: tag names no longer reach a shell as source, and
    the published bundle is now verified against a rebuild before attestation
  • @vercel/ncc 0.45.0 and dev-dependency bumps

v5.0.0
contains these same fixes plus a breaking change: commit subjects render as
literal text, so a merged pull request's subject can no longer inject links or
mentions into your release notes. That change also stops #123 autolinking
inside subjects, which is why it is not on the v4 line.



Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Comment thread .github/workflows/lint-workflows.yml Outdated

- name: Install the latest version of uv
uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2
uses: astral-sh/setup-uv@c771a70e6277c0a99b617c7a806ffedaca235ff9 # v9.0.0
@renovate
renovate Bot force-pushed the renovate/major-github-actions branch from d9e3afb to 134ef7c Compare August 11, 2026 21:52
@renovate renovate Bot changed the title Update astral-sh/setup-uv action to v9 Update astral-sh/setup-uv action to v10 Aug 12, 2026
@renovate
renovate Bot force-pushed the renovate/major-github-actions branch 2 times, most recently from 826dbca to eb82d25 Compare August 14, 2026 20:31
@renovate renovate Bot changed the title Update astral-sh/setup-uv action to v10 Update github-actions (major) Aug 26, 2026
@renovate
renovate Bot force-pushed the renovate/major-github-actions branch from eb82d25 to 906c8df Compare August 26, 2026 07:10
- name: Generate changelog
id: changelog
uses: metcalfc/changelog-generator@98b12822c5dc6bad335d1d60d920cb69831b9c5d # v4.8.0
uses: metcalfc/changelog-generator@031a6408a9ad7fa6dcda49b7222ab2b54110a680 # v5.0.1
@renovate
renovate Bot force-pushed the renovate/major-github-actions branch from 906c8df to 23a5e58 Compare August 26, 2026 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant