Repository navigation
v7.0.0
7.0.0 (2026-09-16)
Features
-
support code block line highlighting (commit 9df7e63)
- Parse fence metadata for line highlighting, support custom highlighters, and enable code line numbers by default.
-
replace
.md-editor-darkwith.md-editor[data-theme="dark"]for theme toggling (commit ac44460)
Fixed Bugs
-
disable raw HTML parsing in markdown-it (commit 6c815cb)
-
correct exposed callbacks and update CDN extensions (commit 00fa33a)
-
replace dynamic option evaluation with JSON5 (commit 8e9c201)
- Parse ECharts code blocks as data and require a top-level object.
-
keep code line numbers aligned after wrapping (commit a6b4cab)
Others
-
chore(deps): upgrade @vavt/markdown-theme (commit 4a27763)
-
ci(release): merge npm publish channels into one trusted workflow (commit 529604a)
- npm trusted publishing allows a single trusted workflow per package, so
- beta and latest can no longer live in separate files. Combine them into
- publish.yml and pick the npm dist-tag from the trigger: a v* tag
- publishes latest, a push to beta publishes with --tag beta.
- Authentication moves from the long-lived NPM_TOKEN secret to OIDC via
- id-token: write. Node 26 ships npm 11.19.0, above the 11.5.1 minimum for
- the token exchange.
- Extract the release-notes and issue-notification logic into
- .github/scripts/ so the workflow file stays focused on orchestration.
- Both scripts walk the commit history between tags, so checkout keeps
- fetch-depth: 0 -- a shallow clone resolves no previous tag and silently
- produces an empty release entry.
- Serialize runs with a concurrency group since publishing and the
- CHANGELOG write-back both mutate remote state.
- Note: the trusted publisher entry on npm must be repointed from
- latest.yml to publish.yml, otherwise publishing fails with E404.
Full Changelog: v6.5.6...v7.0.0