Skip to content

chore(deps): lock file maintenance#726

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/lock-file-maintenance
Open

chore(deps): lock file maintenance#726
renovate[bot] wants to merge 1 commit intomainfrom
renovate/lock-file-maintenance

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 17, 2025

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: Branch creation - "before 4am on monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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.

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Nov 17, 2025

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
ccusage-guide ffd6925 Feb 02 2026, 09:37 PM

@coderabbitai
Copy link

coderabbitai bot commented Nov 17, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

  • 🔍 Trigger a full review

Comment @coderabbitai help to get the list of available commands and usage tips.

@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from 029be54 to 4f10026 Compare November 20, 2025 11:11
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 4f10026 to ed94e70 Compare November 25, 2025 14:35
@pkg-pr-new
Copy link

pkg-pr-new bot commented Nov 25, 2025

Open in StackBlitz

@ccusage/amp

npm i https://pkg.pr.new/ryoppippi/ccusage/@ccusage/amp@726

ccusage

npm i https://pkg.pr.new/ryoppippi/ccusage@726

@ccusage/codex

npm i https://pkg.pr.new/ryoppippi/ccusage/@ccusage/codex@726

@ccusage/mcp

npm i https://pkg.pr.new/ryoppippi/ccusage/@ccusage/mcp@726

@ccusage/opencode

npm i https://pkg.pr.new/ryoppippi/ccusage/@ccusage/opencode@726

@ccusage/pi

npm i https://pkg.pr.new/ryoppippi/ccusage/@ccusage/pi@726

commit: e96c9e0

@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 8 times, most recently from d54edea to ad95e5e Compare December 1, 2025 16:06
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 8 times, most recently from 9742f74 to ac3183b Compare December 9, 2025 18:58
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 5e0c9c5 to 58e0c9d Compare December 11, 2025 17:37
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 4 times, most recently from 62c78be to 57110f1 Compare December 18, 2025 19:53
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from 6df8bde to c837d65 Compare December 29, 2025 05:16
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 4 times, most recently from 75be4ca to 16571f4 Compare January 3, 2026 21:19
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 14 times, most recently from 9c5048e to ed58a66 Compare January 9, 2026 13:02
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from ed58a66 to a0f6bfc Compare February 1, 2026 10:51
@renovate
Copy link
Contributor Author

renovate bot commented Feb 1, 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 10 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 39, reused 0, downloaded 0, added 0
Progress: resolved 56, reused 0, downloaded 0, added 0
Progress: resolved 57, reused 0, downloaded 0, added 0
Progress: resolved 167, reused 0, downloaded 0, added 0
Progress: resolved 234, reused 0, downloaded 0, added 0
Progress: resolved 329, reused 0, downloaded 0, added 0
 ERR_PNPM_TRUST_DOWNGRADE  High-risk trust downgrade for "@octokit/plugin-paginate-rest@9.2.2" (possible package takeover)

This error happened while installing the dependencies of pkg-pr-new@0.0.60
 at @octokit/action@6.1.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.

@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from a0f6bfc to e96c9e0 Compare February 2, 2026 04:52
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from e96c9e0 to ffd6925 Compare February 2, 2026 21:35
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