Conversation
9be8758 to
ddd40b8
Compare
e20f517 to
94f92be
Compare
43b7381 to
086d5ec
Compare
8693803 to
98c5be9
Compare
ee6542d to
b9c73f0
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1252 +/- ##
=======================================
Coverage 90.81% 90.81%
=======================================
Files 183 183
Lines 17161 17161
Branches 1899 1899
=======================================
Hits 15584 15584
Misses 1567 1567
Partials 10 10 ☔ View full report in Codecov by Sentry. |
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@packages/kg-default-nodes/package.json`:
- Line 40: Remove the production dependency entry for "html-minifier" from
package.json and ensure it exists only under devDependencies; specifically,
delete the "html-minifier" key from the dependencies block and keep/add it in
the devDependencies block so that tests (e.g., test utilities importing
html-minifier in packages/kg-default-nodes/test/test-utils/assertions.js) retain
access but production installs won't include it.
In `@packages/kg-markdown-html-renderer/package.json`:
- Around line 32-39: Update the pinned dependency "markdown-it" in package.json
from "14.0.0" to "14.1.0"; locate the dependency entry for "markdown-it" in the
packages/kg-markdown-html-renderer package.json and change its version string to
"14.1.0", then run your install/lockfile update (e.g., npm/yarn/pnpm install)
and ensure tests/build still pass.
🧹 Nitpick comments (2)
packages/koenig-lexical/package.json (2)
70-78: Mixed Storybook versions may cause compatibility issues.Storybook packages are pinned to different versions:
@storybook/addon-*packages:8.5.0(lines 70-74)@storybook/builder-vite,@storybook/react,@storybook/react-vite:8.6.15(lines 75-77)storybook:8.6.15(line 125)Mixing minor versions within the Storybook ecosystem can lead to subtle compatibility issues. Consider aligning all Storybook packages to the same minor version.
52-52: Migrate to@babel/plugin-transform-private-property-in-object.
@babel/plugin-proposal-private-property-in-objectis deprecated. Babel recommends switching to@babel/plugin-transform-private-property-in-objectsince the proposal was merged into the ECMAScript standard. Consider updating in a future iteration.
| "markdown-it": "14.0.0", | ||
| "markdown-it-footnote": "4.0.0", | ||
| "markdown-it-image-lazy-loading": "2.0.1", | ||
| "markdown-it-lazy-headers": "0.1.3", | ||
| "markdown-it-mark": "4.0.0", | ||
| "markdown-it-sub": "2.0.0", | ||
| "markdown-it-sup": "2.0.0", | ||
| "semver": "7.7.3" |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check latest versions on npm for all pinned packages
packages=(
"markdown-it"
"markdown-it-footnote"
"markdown-it-image-lazy-loading"
"markdown-it-lazy-headers"
"markdown-it-mark"
"markdown-it-sub"
"markdown-it-sup"
"semver"
)
echo "=== Checking Latest Versions on npm ==="
for pkg in "${packages[@]}"; do
latest=$(npm view "$pkg" version 2>/dev/null)
if [ $? -eq 0 ]; then
echo "$pkg: $latest"
else
echo "$pkg: ERROR fetching version"
fi
doneRepository: TryGhost/Koenig
Length of output: 300
Update markdown-it to 14.1.0.
Most dependencies are pinned to their latest versions, but markdown-it is one patch version behind. The latest is 14.1.0, while this pins 14.0.0. Consider updating to the latest patch for any bug fixes or improvements it may include, unless there's a specific reason to avoid it.
The other seven dependencies (markdown-it-footnote, markdown-it-image-lazy-loading, markdown-it-lazy-headers, markdown-it-mark, markdown-it-sub, markdown-it-sup, and semver) are all at their current latest versions, which is good for reproducibility.
🤖 Prompt for AI Agents
In `@packages/kg-markdown-html-renderer/package.json` around lines 32 - 39, Update
the pinned dependency "markdown-it" in package.json from "14.0.0" to "14.1.0";
locate the dependency entry for "markdown-it" in the
packages/kg-markdown-html-renderer package.json and change its version string to
"14.1.0", then run your install/lockfile update (e.g., npm/yarn/pnpm install)
and ensure tests/build still pass.
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@packages/kg-unsplash-selector/package.json`:
- Line 36: Update the `@playwright/test` dependency in the koenig-lexical package
to match 1.58.0: open packages/koenig-lexical/package.json, find the
"@playwright/test" entry (currently "1.50.1") and change its version string to
"1.58.0", then run the workspace package manager install command to update
lockfiles and deduplicate node_modules.
In `@packages/koenig-lexical/package.json`:
- Around line 70-78: The Storybook dependencies in package.json are using mixed
minor versions; update the mismatched packages so all `@storybook/`* entries use
the same exact version (either upgrade "@storybook/addon-actions",
"@storybook/addon-essentials", "@storybook/addon-interactions",
"@storybook/addon-links", and "@storybook/addon-mdx-gfm" to "8.6.15" to match
"@storybook/builder-vite", "@storybook/react", "@storybook/react-vite" and
"storybook", or downgrade the 8.6.15 packages to 8.5.0); edit the dependency
entries for the symbols listed in the diff (the five addon entries and the
builder/react/react-vite entries) so they all share one version string and then
run your package manager install to lock the change.
🧹 Nitpick comments (1)
packages/koenig-lexical/package.json (1)
52-52: Consider removing@babel/plugin-proposal-private-property-in-object—it's deprecated and appears unused.The proposal plugin is deprecated in favor of
@babel/plugin-transform-private-property-in-object, and the functionality is included in@babel/preset-envas of Babel 7.21+. Since this project uses Vite (not Babel) and has no Babel configuration or@babel/preset-env, this devDependency appears to be unused and can be safely removed.
| }, | ||
| "devDependencies": { | ||
| "@playwright/test": "^1.48.2", | ||
| "@playwright/test": "1.58.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Find all `@playwright/test` version specifications across the monorepo
rg '"@playwright/test"' --type json -A1 -B1Repository: TryGhost/Koenig
Length of output: 485
🌐 Web query:
@playwright/test latest stable version 2025 2026
💡 Result:
As of January 27, 2026, the latest stable (npm latest tag) version of @playwright/test is 1.58.0. [1] [2]
Pre-release builds newer than that (e.g., 1.59.0-alpha-*) exist, but they are not stable. [2]
Install stable:
npm i -D `@playwright/test`@latestSources: [1] [2]
Align @playwright/test versions across packages: upgrade koenig-lexical to 1.58.0.
This package uses @playwright/test@1.58.0 (the latest stable version), while packages/koenig-lexical/package.json uses 1.50.1. Having different versions of the testing framework across the monorepo risks inconsistent test behavior and unnecessary duplication in node_modules.
Update koenig-lexical to 1.58.0 to match.
🤖 Prompt for AI Agents
In `@packages/kg-unsplash-selector/package.json` at line 36, Update the
`@playwright/test` dependency in the koenig-lexical package to match 1.58.0: open
packages/koenig-lexical/package.json, find the "@playwright/test" entry
(currently "1.50.1") and change its version string to "1.58.0", then run the
workspace package manager install command to update lockfiles and deduplicate
node_modules.
packages/koenig-lexical/package.json
Outdated
| "@storybook/addon-actions": "8.5.0", | ||
| "@storybook/addon-essentials": "8.5.0", | ||
| "@storybook/addon-interactions": "8.5.0", | ||
| "@storybook/addon-links": "8.5.0", | ||
| "@storybook/addon-mdx-gfm": "8.5.0", | ||
| "@storybook/builder-vite": "8.6.15", | ||
| "@storybook/react": "^8.6.14", | ||
| "@storybook/react": "8.6.15", | ||
| "@storybook/react-vite": "8.6.15", | ||
| "@storybook/test-runner": "^0.24.1", | ||
| "@storybook/test-runner": "0.24.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat packages/koenig-lexical/package.json | head -150Repository: TryGhost/Koenig
Length of output: 5131
🌐 Web query:
Storybook 8.5.0 8.6.15 addon compatibility mixed versions
💡 Result:
Storybook addons are not guaranteed to work when you mix Storybook minor/patch versions (e.g. core/framework at 8.5.0 while some @storybook/* addons are 8.6.15). In practice, mismatches can produce “incompatible packages” warnings and hard runtime/build failures due to internal API/import changes. (github.com)
What’s recommended/expected:
- Keep all Storybook packages aligned:
storybook+ your framework package (e.g.@storybook/react,@storybook/nextjs, etc.) + all@storybook/addon-*should be on the same exact version (same8.6.15, or same8.5.0, etc.). This is the safest approach and avoids duplicate/competing Storybook internals. (github.com) - Prefer upgrading to the latest minor in a major line (8.6.x rather than 8.5.x), because Storybook typically only patches the latest minor within the current major—older minors may not receive fixes. (storybook.js.org)
Practical options for your case (8.5.0 vs 8.6.15):
- Upgrade everything to 8.6.15 (recommended), or
- Downgrade the 8.6.15 addons to 8.5.0 so every
@storybook/*matches.
If you’re using pnpm/yarn/npm and versions keep drifting, enforce alignment with your package manager’s overrides/resolutions (single version for all @storybook/*).
Citations:
- 1: [Documentation]: Following Introduction tutorial results in error. storybookjs/storybook#29022
- 2: 🧩 Storybook 8 community addon outreach storybookjs/storybook#26031
- 3: https://storybook.js.org/docs/releases?utm_source=openai
Align all Storybook packages to the same version; mixing 8.5.0 and 8.6.15 can cause build failures.
The Storybook ecosystem packages are pinned to mismatched versions:
@storybook/addon-actions,@storybook/addon-essentials,@storybook/addon-interactions,@storybook/addon-links,@storybook/addon-mdx-gfm→8.5.0@storybook/builder-vite,@storybook/react,@storybook/react-vite→8.6.15storybook→8.6.15
Mixing Storybook minor versions is not supported and can produce "incompatible packages" warnings and hard runtime/build failures due to internal API changes. All @storybook/* packages must be on the same exact version. Upgrade the 8.5.0 addon packages to 8.6.15, or downgrade the 8.6.15 packages to 8.5.0.
🤖 Prompt for AI Agents
In `@packages/koenig-lexical/package.json` around lines 70 - 78, The Storybook
dependencies in package.json are using mixed minor versions; update the
mismatched packages so all `@storybook/`* entries use the same exact version
(either upgrade "@storybook/addon-actions", "@storybook/addon-essentials",
"@storybook/addon-interactions", "@storybook/addon-links", and
"@storybook/addon-mdx-gfm" to "8.6.15" to match "@storybook/builder-vite",
"@storybook/react", "@storybook/react-vite" and "storybook", or downgrade the
8.6.15 packages to 8.5.0); edit the dependency entries for the symbols listed in
the diff (the five addon entries and the builder/react/react-vite entries) so
they all share one version string and then run your package manager install to
lock the change.
🤖 Velo CI Failure AnalysisClassification: 🔴 HARD FAIL
|
🤖 Velo CI Failure AnalysisClassification: 🟠 SOFT FAIL
|
🤖 Velo CI Failure AnalysisClassification: 🔴 HARD FAIL
|
🤖 Velo CI Failure AnalysisClassification: 🔴 HARD FAIL
|
🤖 Velo CI Failure AnalysisClassification: 🔴 HARD FAIL
|
🤖 Velo CI Failure AnalysisClassification: 🔴 HARD FAIL
|
🤖 Velo CI Failure AnalysisClassification: 🔴 HARD FAIL
|
🤖 Velo CI Failure AnalysisClassification: 🔴 HARD FAIL
|
🤖 Velo CI Failure AnalysisClassification: 🔴 HARD FAIL
|
🤖 Velo CI Failure AnalysisClassification: 🟠 SOFT FAIL
|
This PR contains the following updates:
^7.21.11→7.21.11^7.27.1→7.28.6^1.1.2→1.2.1^1.1.1→1.1.1^8.0.0→8.0.0^1.2.2→1.2.3^3.1.0→3.1.1^1.58.0→1.58.2^0.6.0→0.6.1^9.0.0→9.0.8^8.5.0→8.6.14^8.5.0→8.6.14^10.2.16→10.2.19^8.5.0→8.6.14^10.2.16→10.2.19^4.23.0→4.25.8^2.0.0→2.1.1^6.0.1→6.0.2^9.2.0→9.2.1^4.0.0→4.1.0*→4.4.3^3.3.2→3.3.3^17.3.1→17.3.1^5.5.2→5.6.0^10.2.16→10.2.19^5.0.1→5.0.4^9.4.0→9.5.0*→5.0.1*→2.6.1*→5.0.1*→2.0.12*→3.0.1*→2.1.0^4.7.6→4.7.8^4.0.0→4.0.0^4.0.0→4.0.0^29.0.0→29.0.0^29.0.0→29.0.0^10.0.0→10.0.1^4.17.21→4.17.23^3.5.0→3.7.2^14.0.0→14.1.1^4.0.0→4.0.0^2.0.0→2.0.1^0.1.3→0.1.3^4.0.0→4.0.0^2.0.0→2.0.0^2.0.0→2.0.0^0.7.0→0.7.2^8.0.0→8.0.0^1.0.0→1.0.0^18.2.0→18.3.1^5.6.1→5.6.1^18.2.0→18.3.1^0.15.0→0.15.0^2.0.6→2.0.6^7.7.3→7.7.4^1.4.0→1.4.0^10.2.16→10.2.19*→1.0.1*→2.0.0^3.0.0→3.0.0^13.6.28→13.6.30Add the preset
:preserveSemverRangesto your config if you don't want to pin your dependencies.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.