Skip to content

Pin dependencies#1252

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/pin-dependencies
Open

Pin dependencies#1252
renovate[bot] wants to merge 1 commit intomainfrom
renovate/pin-dependencies

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented May 27, 2024

This PR contains the following updates:

Package Type Update Change
@babel/plugin-proposal-private-property-in-object (source) devDependencies pin ^7.21.117.21.11
@babel/plugin-syntax-import-assertions (source) devDependencies pin ^7.27.17.28.6
@emoji-mart/data (source) devDependencies pin ^1.1.21.2.1
@emoji-mart/react (source) devDependencies pin ^1.1.11.1.1
@etchteam/storybook-addon-status devDependencies pin ^8.0.08.0.0
@lezer/highlight devDependencies pin ^1.2.21.2.3
@mdx-js/rollup (source) devDependencies pin ^3.1.03.1.1
@playwright/test (source) devDependencies pin ^1.58.01.58.2
@prettier/sync devDependencies pin ^0.6.00.6.1
@storybook/addon-actions (source) devDependencies pin ^9.0.09.0.8
@storybook/addon-essentials (source) devDependencies pin ^8.5.08.6.14
@storybook/addon-interactions (source) devDependencies pin ^8.5.08.6.14
@storybook/addon-links (source) devDependencies pin ^10.2.1610.2.19
@storybook/addon-mdx-gfm (source) devDependencies pin ^8.5.08.6.14
@storybook/react (source) devDependencies pin ^10.2.1610.2.19
@uiw/react-codemirror (source) devDependencies pin ^4.23.04.25.8
clsx devDependencies pin ^2.0.02.1.1
codemirror devDependencies pin ^6.0.16.0.2
concurrently devDependencies pin ^9.2.09.2.1
cross-fetch devDependencies pin ^4.0.04.1.0
debug devDependencies pin *4.4.3
dompurify devDependencies pin ^3.3.23.3.3
dotenv devDependencies pin ^17.3.117.3.1
emoji-mart (source) devDependencies pin ^5.5.25.6.0
eslint-plugin-storybook (source) devDependencies pin ^10.2.1610.2.19
eventemitter3 devDependencies pin ^5.0.15.0.4
fast-average-color devDependencies pin ^9.4.09.5.0
gulp (source) devDependencies pin *5.0.1
gulp-concat devDependencies pin *2.6.1
gulp-debug devDependencies pin *5.0.1
gulp-header devDependencies pin *2.0.12
gulp-jsbeautifier devDependencies pin *3.0.1
gulp-rename devDependencies pin *2.1.0
handlebars (source) dependencies pin ^4.7.64.7.8
html-minifier (source) devDependencies pin ^4.0.04.0.0
html-minifier (source) dependencies pin ^4.0.04.0.0
jsdom devDependencies pin ^29.0.029.0.0
jsdom dependencies pin ^29.0.029.0.0
juice dependencies pin ^10.0.010.0.1
lodash (source) dependencies pin ^4.17.214.17.23
luxon dependencies pin ^3.5.03.7.2
markdown-it dependencies pin ^14.0.014.1.1
markdown-it-footnote dependencies pin ^4.0.04.0.0
markdown-it-image-lazy-loading dependencies pin ^2.0.02.0.1
markdown-it-lazy-headers dependencies pin ^0.1.30.1.3
markdown-it-mark dependencies pin ^4.0.04.0.0
markdown-it-sub dependencies pin ^2.0.02.0.0
markdown-it-sup dependencies pin ^2.0.02.0.0
mobiledoc-dom-renderer dependencies pin ^0.7.00.7.2
pluralize devDependencies pin ^8.0.08.0.0
prettier-plugin-organize-attributes devDependencies pin ^1.0.01.0.0
react (source) devDependencies pin ^18.2.018.3.1
react-colorful (source) devDependencies pin ^5.6.15.6.1
react-dom (source) devDependencies pin ^18.2.018.3.1
react-highlight devDependencies pin ^0.15.00.15.0
react-slider devDependencies pin ^2.0.62.0.6
semver dependencies pin ^7.7.37.7.4
simple-dom dependencies pin ^1.4.01.4.0
storybook (source) devDependencies pin ^10.2.1610.2.19
vinyl-buffer devDependencies pin *1.0.1
vinyl-source-stream devDependencies pin *2.0.0
y-websocket devDependencies pin ^3.0.03.0.0
yjs (source) devDependencies pin ^13.6.2813.6.30

⚠️ Renovate's pin functionality does not currently wire in the release age for a package, so the Minimum Release Age checks can apply. You will need to manually validate the Minimum Release Age for these package(s).

Add the preset :preserveSemverRanges to 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/pin-dependencies branch 19 times, most recently from 9be8758 to ddd40b8 Compare May 31, 2024 14:22
@renovate renovate bot force-pushed the renovate/pin-dependencies branch 8 times, most recently from e20f517 to 94f92be Compare June 11, 2024 10:14
@renovate renovate bot force-pushed the renovate/pin-dependencies branch 3 times, most recently from 43b7381 to 086d5ec Compare June 12, 2024 12:10
@renovate renovate bot force-pushed the renovate/pin-dependencies branch 12 times, most recently from 8693803 to 98c5be9 Compare July 2, 2024 18:04
@renovate renovate bot force-pushed the renovate/pin-dependencies branch 3 times, most recently from ee6542d to b9c73f0 Compare July 4, 2024 10:15
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.81%. Comparing base (c118424) to head (b278c1b).

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.
📢 Have feedback on the report? Share it here.

@coderabbitai
Copy link

coderabbitai bot commented Jan 21, 2025

Important

Review skipped

Bot user detected.

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

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c8622319-dffa-4006-ad1c-d751c53335e4

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

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch renovate/pin-dependencies
📝 Coding Plan
  • Generate coding plan for human review comments

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.

❤️ Share

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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-object is deprecated. Babel recommends switching to @babel/plugin-transform-private-property-in-object since the proposal was merged into the ECMAScript standard. Consider updating in a future iteration.

Comment on lines +32 to +39
"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"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

🧩 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
done

Repository: 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-env as 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",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Find all `@playwright/test` version specifications across the monorepo
rg '"@playwright/test"' --type json -A1 -B1

Repository: 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`@latest

Sources: [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.

Comment on lines +70 to +78
"@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",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

cat packages/koenig-lexical/package.json | head -150

Repository: 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 (same 8.6.15, or same 8.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):

  1. Upgrade everything to 8.6.15 (recommended), or
  2. 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:


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-gfm8.5.0
  • @storybook/builder-vite, @storybook/react, @storybook/react-vite8.6.15
  • storybook8.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.

@ErisDS
Copy link
Member

ErisDS commented Mar 2, 2026

🤖 Velo CI Failure Analysis

Classification: 🔴 HARD FAIL

  • Workflow: Test
  • Failed Step: Get installed Playwright version
  • Run: View failed run
    What failed: Unable to get installed Playwright version due to invalid format
    Why: The failure is caused by an issue with extracting the Playwright version from the yarn.lock file. This is likely an infrastructure issue, as it's not related to the application code itself.
    Action:
    Check the yarn.lock file format or the script used to extract the Playwright version. If the issue persists, it may be necessary to investigate the CI environment or the Playwright installation process.

@ErisDS
Copy link
Member

ErisDS commented Mar 2, 2026

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

  • Workflow: Test
  • Failed Step: Get installed Playwright version
  • Run: View failed run
    What failed: Unable to process file command 'env' successfully due to invalid format '1.58.2'
    Why: The failure is caused by an issue with processing the 'env' command, specifically due to an invalid format '1.58.2' in the Playwright version. This is a code-related issue, as the script responsible for extracting the Playwright version from the yarn.lock file is not handling the version format correctly.
    Action:
    The author should review the script that extracts the Playwright version and update it to handle the version format correctly. This will likely resolve the issue and allow the CI step to pass.

@ErisDS
Copy link
Member

ErisDS commented Mar 2, 2026

🤖 Velo CI Failure Analysis

Classification: 🔴 HARD FAIL

  • Workflow: Test
  • Failed Step: Get installed Playwright version
  • Run: View failed run
    What failed: Unable to process file command 'env' successfully due to invalid Playwright version format
    Why: The failure is caused by an issue with the Playwright version format, which is not being processed correctly by the CI environment. This is an infrastructure-related problem, not a code issue.
    Action:
    Check the Playwright version format in the CI environment and ensure it matches the expected format. If the issue persists, investigate the CI configuration and environment setup.

@ErisDS
Copy link
Member

ErisDS commented Mar 3, 2026

🤖 Velo CI Failure Analysis

Classification: 🔴 HARD FAIL

  • Workflow: Test
  • Failed Step: Get installed Playwright version
  • Run: View failed run
    What failed: Unable to process file command 'env' successfully due to invalid Playwright version format
    Why: The failure is caused by an issue with the Playwright version format, which is not in the expected format. This is an infrastructure issue, as it is not related to the code itself but rather to the environment or tooling used in the CI pipeline.
    Action:
    Check the Playwright version format in the CI pipeline and ensure it is in the expected format. If the issue persists, investigate the CI environment and tooling to identify and resolve the root cause.

@ErisDS
Copy link
Member

ErisDS commented Mar 3, 2026

🤖 Velo CI Failure Analysis

Classification: 🔴 HARD FAIL

  • Workflow: Test
  • Failed Step: Get installed Playwright version
  • Run: View failed run
    What failed: Unable to process file command 'env' successfully due to invalid Playwright version format
    Why: The failure is caused by an issue with the Playwright version format, which is not in the expected format. This is an infrastructure issue, as it is not related to the code but rather to the environment or the way the Playwright version is being retrieved.
    Action:
    Check the Playwright version format in the logs and update the script to handle the unexpected format correctly. If the issue persists, investigate the Playwright installation process or the environment where the CI is running.

@ErisDS
Copy link
Member

ErisDS commented Mar 3, 2026

🤖 Velo CI Failure Analysis

Classification: 🔴 HARD FAIL

  • Workflow: Test
  • Failed Step: Get installed Playwright version
  • Run: View failed run
    What failed: Unable to process file command 'env' successfully due to invalid Playwright version format
    Why: The failure is caused by an issue with the Playwright version format, which is not in the expected format. This is an infrastructure issue, as it is not related to the code itself but rather to the environment or tooling used in the CI pipeline.
    Action:
    Check the Playwright version format in the CI pipeline and ensure it is in the correct format. If the issue persists, investigate the CI environment and tooling to identify the root cause.

@ErisDS
Copy link
Member

ErisDS commented Mar 3, 2026

🤖 Velo CI Failure Analysis

Classification: 🔴 HARD FAIL

  • Workflow: Test
  • Failed Step: Get installed Playwright version
  • Run: View failed run
    What failed: Unable to get installed Playwright version due to invalid format
    Why: The failure is caused by an issue with extracting the Playwright version from the yarn.lock file. This is likely an infrastructure issue, as it's not related to the application code itself.
    Action:
    Check the yarn.lock file format or the script used to extract the Playwright version. If the issue persists, it may be necessary to investigate the CI environment or the Playwright installation process.

@ErisDS
Copy link
Member

ErisDS commented Mar 3, 2026

🤖 Velo CI Failure Analysis

Classification: 🔴 HARD FAIL

  • Workflow: Test
  • Failed Step: Get installed Playwright version
  • Run: View failed run
    What failed: Unable to process file command 'env' successfully due to invalid Playwright version format
    Why: The failure is caused by an issue with the Playwright version format, which is not in the expected format. This is an infrastructure issue, as it is not related to the code itself but rather to the environment or tooling used in the CI pipeline.
    Action:
    Investigate the Playwright version detection logic in the CI pipeline and ensure that the version format is correctly parsed. Consider adding error handling or fallback logic to handle unexpected version formats.

@ErisDS
Copy link
Member

ErisDS commented Mar 4, 2026

🤖 Velo CI Failure Analysis

Classification: 🔴 HARD FAIL

  • Workflow: Test
  • Failed Step: Get installed Playwright version
  • Run: View failed run
    What failed: Unable to process file command 'env' successfully due to invalid Playwright version format
    Why: The failure is caused by an issue with the Playwright version format, which is not in the expected format. This is an infrastructure issue, as it is not related to the code but rather to the environment or the way the Playwright version is being retrieved.
    Action:
    Check the Playwright version format in the workflow and ensure it is in the correct format. If the issue persists, investigate the environment or the way the Playwright version is being retrieved.

@ErisDS
Copy link
Member

ErisDS commented Mar 4, 2026

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

  • Workflow: Test
  • Failed Step: Get installed Playwright version
  • Run: View failed run
    What failed: Failed to get installed Playwright version due to invalid format
    Why: The root cause is that the Playwright version extracted from the yarn.lock file has an invalid format, causing the 'env' command to fail. This is a code issue, as the code responsible for extracting the version is not handling the format correctly.
    Action:
    The author should investigate the yarn.lock file and the code that extracts the Playwright version, and fix the issue to ensure the version is extracted correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants