Skip to content

chore(deps): update devdependency bumpp to v11#686

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/bumpp-11.x
Open

chore(deps): update devdependency bumpp to v11#686
renovate[bot] wants to merge 1 commit intomainfrom
renovate/bumpp-11.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 16, 2026

This PR contains the following updates:

Package Change Age Confidence
bumpp 10.4.111.0.1 age confidence

Warning

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


Release Notes

antfu-collective/bumpp (bumpp)

v11.0.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v11.0.0

Compare Source

   🚨 Breaking Changes
    View changes on GitHub

Configuration

📅 Schedule: Branch creation - "on Monday" (UTC), 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.

@vercel
Copy link

vercel bot commented Mar 16, 2026

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

Project Deployment Actions Updated (UTC)
magic-regexp-docs Error Error Mar 16, 2026 6:34am

@renovate
Copy link
Contributor Author

renovate bot commented Mar 16, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Scope: all 3 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 24, reused 0, downloaded 0, added 0
Progress: resolved 27, reused 0, downloaded 0, added 0
Progress: resolved 114, reused 0, downloaded 0, added 0
Progress: resolved 201, reused 0, downloaded 0, added 0
Progress: resolved 290, reused 0, downloaded 0, added 0
Progress: resolved 378, reused 0, downloaded 0, added 0
Progress: resolved 463, reused 0, downloaded 0, added 0
Progress: resolved 505, reused 0, downloaded 0, added 0
Progress: resolved 566, reused 0, downloaded 0, added 0
Progress: resolved 668, reused 0, downloaded 0, added 0
Progress: resolved 686, reused 0, downloaded 0, added 0
Progress: resolved 706, reused 0, downloaded 0, added 0
Progress: resolved 747, reused 0, downloaded 0, added 0
Progress: resolved 821, reused 0, downloaded 0, added 0
Progress: resolved 881, reused 0, downloaded 0, added 0
Progress: resolved 909, reused 0, downloaded 0, added 0
Progress: resolved 1047, reused 0, downloaded 0, added 0
Progress: resolved 1062, reused 0, downloaded 0, added 0
Progress: resolved 1105, reused 0, downloaded 0, added 0
Progress: resolved 1231, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/unjs/magic-regexp/docs:
 ERR_PNPM_TRUST_DOWNGRADE  High-risk trust downgrade for "semver@6.3.1" (possible package takeover)

This error happened while installing the dependencies of nuxt@4.3.1
 at @nuxt/vite-builder@4.3.1
 at @vitejs/plugin-vue-jsx@5.1.4
 at @babel/core@7.29.0

Trust checks are based solely on publish date, not semver. A package cannot be installed if any earlier-published version had stronger trust evidence. Earlier versions had provenance attestation, but this version has no trust evidence. A trust downgrade may indicate a supply chain incident.

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.

0 participants