Skip to content

chore(deps): update tj-actions/changed-files digest to 24d32ff - #1915

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/tj-actions-changed-files-digest
Closed

chore(deps): update tj-actions/changed-files digest to 24d32ff#1915
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/tj-actions-changed-files-digest

Conversation

@renovate

@renovate renovate Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
tj-actions/changed-files (changelog) action digest 9426d4024d32ff

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday (* 0-4,22-23 * * 1-5)
    • Only on Sunday and Saturday (* * * * 0,6)
  • 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

@renovate
renovate Bot requested a review from a team as a code owner August 12, 2026 22:19
@vercel

vercel Bot commented Aug 12, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
nimbus-documentation Ready Ready Preview Aug 14, 2026 11:25am
nimbus-storybook Ready Ready Preview Aug 14, 2026 11:25am

Request Review

@changeset-bot

changeset-bot Bot commented Aug 12, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 9bd25e6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions

github-actions Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Bundle Size Report

Last updated: 2026-08-14 11:23:37 UTC

Package Format Current Baseline Delta Status
@commercetools/nimbus dist 18950.9 KB 18950.9 KB +0.0% ✅ ok
@commercetools/nimbus-icons dist 4787.6 KB 4787.6 KB +0.0% ✅ ok
@commercetools/nimbus-tokens dist 408.9 KB 408.9 KB +0.0% ✅ ok

Baseline source: comment-chain

@misama-ct

Copy link
Copy Markdown
Collaborator

Closing — this is a downgrade, not an upgrade.

digest tag date
current pin 9426d409 v47.0.6 2026-04-18
proposed 24d32ffd v47.0.0 2025-09-13

v47.0.6 is the latest tj-actions/changed-files release. Upstream never advanced the floating v47 tag past v47.0.0, so our # v47 pin comment made Renovate resolve that stale ref and "correct" our newer digest backwards — reverting six patch releases, including bump lodash from 4.17.23 to 4.18.1 (tj-actions/changed-files#2837).

Fixed in #1928 by retagging the pin comment to # v47.0.6, which restores proper semver comparison. I audited all nine pinned actions in this repo; this was the only one affected.

@misama-ct misama-ct closed this Aug 18, 2026
@renovate

renovate Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for the tj-actions/changed-files 24d32ff update again.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate
renovate Bot deleted the renovate/tj-actions-changed-files-digest branch August 18, 2026 07:31
ByronDWall pushed a commit that referenced this pull request Aug 18, 2026
…downgrade (#1928)

Renovate opened seven dependency PRs that must never merge. Six of them
(#1917 #1918 #1919 #1920 #1923 #1924) bump pnpm override entries across a
major boundary. Those keys are selectors, not package names: "yaml@1"
means "consumers resolving to yaml v1 get this patched v1", so raising the
value to 2.9.0 forces a v2 API onto v1 consumers. Two are already red in
CI ("TypeError: expand is not a function" for brace-expansion@2 -> ^5.0.0,
and gray-matter's yaml.safeLoad.bind() for js-yaml ^3.15.0 -> ^5.0.0); the
rest are green only because CI never exercises the affected transitive
consumers -- the same blind spot that let #1904 ship the minimatch v10
break that #1913 had to revert, and which #1920 now proposes again.

Renovate also rewrites floor+cap ranges into bare caps
(immutable ">=4.3.9 <5" -> "<6", undici ">=7.28.0 <8" -> "<9"), discarding
the security floor that justified the override.

Suppress majors on override depTypes. Minor/patch still flow so floors can
be raised, and CVE remediation is unaffected because vulnerabilityAlerts
already bypasses packageRules.

Separately, #1915 proposed a tj-actions/changed-files digest "update" that
is really a 7-month downgrade: upstream never moved the floating v47 tag
past v47.0.0, so Renovate resolved our newer v47.0.6 pin backwards.
Retagging the pin comment to the exact patch restores semver comparison.
Audited all nine pinned actions; this was the only one affected.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant