Skip to content

Repository navigation

chore(deps): update dependency vitepress to v2.0.0-alpha.18 - #1517

Merged
renovate[bot] merged 1 commit into
mainfrom
renovate/vitepress-2.x
Jul 28, 2026
Merged

chore(deps): update dependency vitepress to v2.0.0-alpha.18#1517
renovate[bot] merged 1 commit into
mainfrom
renovate/vitepress-2.x

Conversation

@renovate

@renovate renovate Bot commented Jul 28, 2026 •
edited by blacksmith-sh Bot
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
vitepress (source) 2.0.0-alpha.17 → 2.0.0-alpha.18 age confidence

Release Notes

vuejs/vitepress (vitepress)

v2.0.0-alpha.18

Compare Source

Bug Fixes
  • build: apply base to links with download attribute (#​5186) (01987c4)
  • build: normalize rewrite drive letters (#​5245) (5c50b99)
  • build: show dead link line numbers (#​5230) (c37bde6)
  • compose markdown config when extending configs (#​5236) (04f4fba)
  • delete undefined values while merging sidepanel props (cc30b10)
  • disable pluginTimings and invalidAnnotation for now (9315fc1)
  • don't invalidate framework chunk when a new asset is added (c0e2e18)
  • escape description in head (d96bf1d)
  • index rewritten local search pages by locale (#​5241) (80cf265)
  • keep translation links in the current tab (#​5158) (202ee70)
  • normalize /index to / (856858d), closes #​5165
  • preserve Agent Studio DocSearch options (#​5254) (f29ffdb)
  • preserve external sidebar links with base (#​5243) (ddf178a)
  • prevent DocSearch SVG clipping in WebKit (#​5240) (a357e5e)
  • strip frontmatter before heading includes (#​5246) (e68fade)
  • theme: avatars misaligned in team member cards (6730fb8), closes #​5160
  • theme: correct mixed LTR/RTL text rendering in code blocks (73f7b0b)
  • theme: keep external link icon inline (#​5232) (756a88c)
  • theme: prevent sub and sup elements from affecting line height (19357f9), closes #​5173
  • use resolveDynamicComponent instead of resolveComponent (9da1e3e)
Features
BREAKING CHANGES
  • VitePress now uses Vite 8. If you are using Vite plugins in your config, please check the Vite 8 migration guide for any breaking changes that may affect you.
  • Node 20 support is dropped. v22 or higher is needed.
  • scrollOffset from config is removed. Users wanting to customize scroll offset should customize scroll-margin-top via CSS instead. smoothScroll support from router.go is also removed as it didn't work as expected for most users. Users wanting smooth scrolling should set scroll-behavior: smooth in CSS, ideally inside a @media (prefers-reduced-motion: no-preference) block.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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

View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 28, 2026 •
edited
Loading

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

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

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs		 ccusage-guide 9cd0b01 Commit Preview URL

Branch Preview URL		 Jul 28 2026, 11:48 AM

@socket-security

socket-security Bot commented Jul 28, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Addednpm/​vitepress@​2.0.0-alpha.18981008694100

View full report

@socket-security

socket-security Bot commented Jul 28, 2026

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm @emnapi/runtime is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yaml → npm/@ryoppippi/[email protected] → npm/[email protected] → npm/[email protected] → npm/@emnapi/[email protected]

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@emnapi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@pkg-pr-new

pkg-pr-new Bot commented Jul 28, 2026

Copy link
Copy Markdown

Open in StackBlitz

ccusage

npx https://pkg.pr.new/ccusage@1517

@ccusage/ccusage-darwin-arm64

npx https://pkg.pr.new/@ccusage/ccusage-darwin-arm64@1517

@ccusage/ccusage-darwin-x64

npx https://pkg.pr.new/@ccusage/ccusage-darwin-x64@1517

@ccusage/ccusage-linux-arm64

npx https://pkg.pr.new/@ccusage/ccusage-linux-arm64@1517

@ccusage/ccusage-linux-x64

npx https://pkg.pr.new/@ccusage/ccusage-linux-x64@1517

@ccusage/ccusage-win32-x64

npx https://pkg.pr.new/@ccusage/ccusage-win32-x64@1517

commit: 9cd0b01

@github-actions

github-actions Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

ccusage performance comparison

PR SHA: 9cd0b01f2d37
Base SHA: b16676fb0ba7

This compares the PR package against the configured base package on the same CI runner.

Package runtime diagnostics

Compares the PR package wrapper, the installed native optional dependency binary, and the workspace release binary on the same large fixture. This identifies whether slow package results come from JavaScript wrapper overhead, the published native binary build, or the Rust core itself.

Fixtures: Claude /home/runner/_work/_temp/ccusage-large-fixture (1.01 GiB, 2597 files), Codex /home/runner/_work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2597 files)
All rows run --offline --json, measured by hyperfine with 0 warmups and 1 runs. This isolates wrapper overhead from the installed native optional dependency and the workspace release binary built on the runner.

Command Runtime Input Median Throughput Samples
claude --offline --json Package wrapper 1.01 GiB 321.4ms 3.13 GiB/s 1
claude --offline --json Installed native binary 1.01 GiB 315.1ms 3.20 GiB/s 1
codex --offline --json Package wrapper 1.01 GiB 114.8ms 8.77 GiB/s 1
codex --offline --json Installed native binary 1.01 GiB 91.4ms 11.02 GiB/s 1

Committed fixture performance

Committed small fixtures for stable PR-to-PR feedback and explicit Claude/Codex command coverage.

Fixtures: Claude apps/ccusage/test/fixtures/claude (0.00 MiB, 2 files), Codex apps/ccusage/test/fixtures/codex (0.00 MiB, 1 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs the published ccusage package from pkg.pr.new, installed before measurement. Both run --offline --json, measured by hyperfine with 2 warmups and 7 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command Input Base median PR median PR vs base Base peak RSS PR peak RSS PR/base RSS Base throughput PR throughput
claude daily --offline --json 0.00 MiB 31.1ms 27.4ms 1.13x 55.25 MiB 55.00 MiB 1.00x 0.05 MiB/s 0.06 MiB/s
claude session --offline --json 0.00 MiB 24.0ms 24.9ms 0.97x 55.00 MiB 55.00 MiB 1.00x 0.06 MiB/s 0.06 MiB/s
codex daily --offline --json 0.00 MiB 25.5ms 25.4ms 1.00x 54.75 MiB 55.00 MiB 1.00x 0.03 MiB/s 0.03 MiB/s
codex session --offline --json 0.00 MiB 23.3ms 22.8ms 1.02x 55.00 MiB 55.00 MiB 1.00x 0.04 MiB/s 0.04 MiB/s

Large real-world-shaped fixture performance

Generated fixtures shaped from aggregate local log statistics: thousands of JSONL files, many small sessions, and a long tail of larger sessions. No real prompts, paths, or outputs are stored in the fixtures.

Fixtures: Claude /home/runner/_work/_temp/ccusage-large-fixture (1.01 GiB, 2597 files), Codex /home/runner/_work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2597 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs the published ccusage package from pkg.pr.new, installed before measurement. Both run --offline --json, measured by hyperfine with 0 warmups and 1 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command Input Base median PR median PR vs base Base peak RSS PR peak RSS PR/base RSS Base throughput PR throughput
claude --offline --json 1.01 GiB 368.5ms 330.3ms 1.12x 966.58 MiB 956.58 MiB 0.99x 2.73 GiB/s 3.05 GiB/s
codex --offline --json 1.01 GiB 117.7ms 118.2ms 1.00x 416.65 MiB 404.64 MiB 0.97x 8.55 GiB/s 8.52 GiB/s

Artifact size

Artifact Base PR Delta Ratio
packed ccusage-*.tgz 18.78 KiB 18.78 KiB +0.00 KiB 1.00x
installed native package binary 4156.78 KiB 4156.78 KiB +0.00 KiB 1.00x

Lower medians and smaller artifacts are better. CI runner noise still applies; use same-run ratios as directional PR feedback, not release guarantees.

@github-actions

github-actions Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

ccusage performance comparison

PR SHA: 9cd0b01f2d37
Base SHA: b16676fb0ba7

This compares the Rust PR release binary against the configured base package on the same CI runner.

Package runtime diagnostics

Compares the PR package wrapper, the installed native optional dependency binary, and the workspace release binary on the same large fixture. This identifies whether slow package results come from JavaScript wrapper overhead, the published native binary build, or the Rust core itself.

Fixtures: Claude /home/runner/_work/_temp/ccusage-large-fixture (1.01 GiB, 2597 files), Codex /home/runner/_work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2597 files)
All rows run --offline --json, measured by hyperfine with 0 warmups and 1 runs. This isolates wrapper overhead from the installed native optional dependency and the workspace release binary built on the runner.

Command Runtime Input Median Throughput Samples
claude --offline --json Package wrapper 1.01 GiB 337.3ms 2.98 GiB/s 1
claude --offline --json Installed native binary 1.01 GiB 313.4ms 3.21 GiB/s 1
codex --offline --json Package wrapper 1.01 GiB 121.1ms 8.31 GiB/s 1
codex --offline --json Installed native binary 1.01 GiB 96.7ms 10.41 GiB/s 1

Committed fixture performance

Committed small fixtures for stable PR-to-PR feedback and explicit Claude/Codex command coverage.

Fixtures: Claude apps/ccusage/test/fixtures/claude (0.00 MiB, 2 files), Codex apps/ccusage/test/fixtures/codex (0.00 MiB, 1 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs the published native ccusage binary from pkg.pr.new, installed before measurement. Both run --offline --json, measured by hyperfine with 2 warmups and 7 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command Input Base median PR median PR vs base Base peak RSS PR peak RSS PR/base RSS Base throughput PR throughput
claude daily --offline --json 0.00 MiB 32.3ms 5.7ms 5.67x 55.25 MiB 14.45 MiB 0.26x 0.05 MiB/s 0.27 MiB/s
claude session --offline --json 0.00 MiB 25.0ms 3.4ms 7.30x 55.00 MiB 12.45 MiB 0.23x 0.06 MiB/s 0.45 MiB/s
codex daily --offline --json 0.00 MiB 25.1ms 2.4ms 10.25x 55.00 MiB 10.44 MiB 0.19x 0.03 MiB/s 0.35 MiB/s
codex session --offline --json 0.00 MiB 23.5ms 2.4ms 9.67x 55.00 MiB 10.45 MiB 0.19x 0.04 MiB/s 0.35 MiB/s

Large real-world-shaped fixture performance

Generated fixtures shaped from aggregate local log statistics: thousands of JSONL files, many small sessions, and a long tail of larger sessions. No real prompts, paths, or outputs are stored in the fixtures.

Fixtures: Claude /home/runner/_work/_temp/ccusage-large-fixture (1.01 GiB, 2597 files), Codex /home/runner/_work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2597 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs the published native ccusage binary from pkg.pr.new, installed before measurement. Both run --offline --json, measured by hyperfine with 0 warmups and 1 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command Input Base median PR median PR vs base Base peak RSS PR peak RSS PR/base RSS Base throughput PR throughput
claude --offline --json 1.01 GiB 371.4ms 321.0ms 1.16x 948.57 MiB 940.58 MiB 0.99x 2.71 GiB/s 3.14 GiB/s
codex --offline --json 1.01 GiB 120.8ms 97.3ms 1.24x 406.90 MiB 426.65 MiB 1.05x 8.34 GiB/s 10.35 GiB/s

Artifact size

Artifact Base PR Delta Ratio
packed ccusage-*.tgz 18.78 KiB 18.78 KiB +0.00 KiB 1.00x
installed native package binary 4156.78 KiB 4156.78 KiB +0.00 KiB 1.00x

Lower medians and smaller artifacts are better. CI runner noise still applies; use same-run ratios as directional PR feedback, not release guarantees.

@renovate
renovate Bot merged commit b1f8b85 into main Jul 28, 2026
54 checks passed
@renovate
renovate Bot deleted the renovate/vitepress-2.x branch July 28, 2026 12:06
@github-actions github-actions Bot mentioned this pull request Jul 28, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@renovate-approve renovate-approve[bot] renovate-approve[bot] approved these changes

Assignees

No one assigned

Labels

dependencies renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants