Repository navigation
meta: bump @doc-kit/cli from 1.0.4 to 1.0.5 - #186
dependabot[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
👋 Codeowner Review RequestThe following codeowners have been identified for the changed files: Team reviewers: @nodejs/nodejs-website Please review the changes when you have a chance. Thank you! 🙏 |
Bumps [@doc-kit/cli](https://github.com/nodejs/doc-kit/tree/HEAD/packages/cli) from 1.0.4 to 1.0.5. - [Release notes](https://github.com/nodejs/doc-kit/releases) - [Changelog](https://github.com/nodejs/doc-kit/blob/main/packages/cli/CHANGELOG.md) - [Commits](https://github.com/nodejs/doc-kit/commits/@doc-kit/cli@1.0.5/packages/cli) --- updated-dependencies: - dependency-name: "@doc-kit/cli" dependency-version: 1.0.5 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
ae8260f to
d15211f
Compare
Both packages pin an exact @doc-kit/core, and the CLI and the generator have to share one copy: core keeps the resolved config in module state, so a generator reading a second copy gets `undefined` and the build fails with "Cannot read properties of undefined (reading 'orama-db')". Bumping either one alone (#184, #186) leaves core 1.2.1 and 1.3.0 side by side. Moving both lands a single, deduped core 1.3.0, which @node-core/doc-kit 2.0.6 already pins. Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>
|
Superseded by #184, which bumps both doc-kit packages together. They pin an exact |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps @doc-kit/cli from 1.0.4 to 1.0.5.
Release notes
Sourced from @doc-kit/cli's releases.
Changelog
Sourced from @doc-kit/cli's changelog.
Commits