Update Well Known

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
debug	4.3.4 → 4.4.3
fs-extra	11.1.1 → 11.3.4
moment (source)	2.29.4 → 2.30.1
semver	7.7.2 → 7.7.4
yarn	1.22.19 → 1.22.22

---

Release Notes

debug-js/debug (debug)

v4.4.3

Compare Source

Functionally identical release to 4.4.1.

Version 4.4.2 is compromised. Please see #​1005.

v4.4.1

Compare Source

What's Changed

• fix(Issue-996): replace whitespaces in namespaces string with commas globally by @​pdahal-cx in #​997
• fixes #​987 fallback to localStorage.DEBUG if debug is not defined by @​lzilioli in #​988

New Contributors

• @​pdahal-cx made their first contribution in #​997
• @​lzilioli made their first contribution in #​988

Full Changelog: debug-js/debug@4.4.0...4.4.1

v4.4.0

Compare Source

Fixes (hopefully) the inefficient regex warnings in .enable().

Minor version as this is invariably going to break certain users who misuse the .enable() API and expected it to work with regexes, which was never supported nor documented. That's on you, sorry - that functionality won't be added back.

Full Changelog: debug-js/debug@4.3.7...4.4.0

v4.3.7

Compare Source

What's Changed

• Upgrade ms to version 2.1.3 by @​realityking in #​819

Full Changelog: debug-js/debug@4.3.6...4.3.7

v4.3.6

Compare Source

What's Changed

• Avoid using deprecated RegExp.$1 by @​bluwy in #​969

New Contributors

• @​bluwy made their first contribution in #​969

Full Changelog: debug-js/debug@4.3.5...4.3.6

v4.3.5

Compare Source

Patch

• cac39b1 Fix/debug depth (#​926)

Thank you @​calvintwr for the fix.

jprichardson/node-fs-extra (fs-extra)

v11.3.4

Compare Source

• Fix bug where calling ensureSymlink/ensureSymlinkSync with a relative srcPath would fail if the symlink already existed (#​1038, #​1064)

v11.3.3

Compare Source

• Fix copying symlink when destination is a symlink to the same target (#​1019, #​1060)

v11.3.2

Compare Source

• Fix spurrious UnhandledPromiseRejectionWarning that could occur when calling .copy() in some cases (#​1056, #​1058)

v11.3.1

Compare Source

• Fix case where move/moveSync could incorrectly think files are identical on Windows (#​1050)

v11.3.0

Compare Source

• Add promise support for newer fs methods (#​1044, #​1045)
• Use fs.opendir in copy()/copySync() for better perf/scalability (#​972, #​1028)

v11.2.0

Compare Source

• Copy directory contents in parallel for better performance (#​1026)
• Refactor internal code to use async/await (#​1020)

moment/moment (moment)

v2.30.1

Compare Source

• Release Dec 27, 2023
• Revert #​5827, because it's breaking
  a lot of TS code.

v2.30.0

Compare Source

• Release Dec 26, 2023

npm/node-semver (semver)

v7.7.4

Compare Source

Bug Fixes

• a29faa5 #​835 cli: pass options to semver.valid() for loose version validation (#​835) (@​mldangelo)

Documentation

• 1d28d5e #​836 fix typos and update -n CLI option documentation (#​836) (@​mldangelo)

Dependencies

• 120968b #​840 @npmcli/template-oss@4.29.0 (#​840)

Chores

• 44d7130 #​824 bump @​npmcli/eslint-config from 5.1.0 to 6.0.0 (#​824) (@​dependabot[bot])
• 7073576 #​820 reorder parameters in invalid-versions.js test (#​820) (@​reggi)
• 5816d4c #​829 bump @​npmcli/template-oss from 4.28.0 to 4.28.1 (#​829) (@​dependabot[bot], @​npm-cli-bot)

v7.7.3

Compare Source

Bug Fixes

• e37e0ca #​813 faster paths for compare (#​813) (@​H4ad)
• 2471d75 #​811 x-range build metadata support (i529015)

Chores

• 8f05c87 #​807 bump @​npmcli/template-oss from 4.25.0 to 4.25.1 (#​807) (@​dependabot[bot], @​owlstronaut)

yarnpkg/yarn (yarn)

v1.22.22

Compare Source

• Fixes a punycode warning.

• Fixes a hoisting issue when transitive dependencies themselves listed aliases as dependencies.

v1.22.21

Compare Source

[!WARNING]
This release is missing a couple of artifacts (the .msi/.rpm/.deb/.asc files); we're working on fixing this.

• Fixes an issue in the v1.22.20 when calling Yarn from a project subfolder, outside of a Corepack context.

• Added a SKIP_YARN_COREPACK_CHECK environment variable to skip the Corepack check.

v1.22.20

Compare Source

[!WARNING]
This release is missing a couple of artifacts (the .msi/.rpm/.deb/.asc files); we're working on fixing this.

• Important: Punycode is now embed within the bundle, as it has been deprecated by Node.js and will be removed in a future version.

• A message will be displayed when Yarn 1.22 notices that the local project has a package.json file referencing a non-1.x Yarn release via the packageManager field. The message will explain that the project is intended to be used with Corepack.

• The yarn-error.log files won't be generated anymore, as we don't process non-critical 1.x bug reports (we however process all bugs reported on https://github.com/yarnpkg/berry; we just released the 4.0.2 release there).

• The yarn set version x.y.z command will now install the exact x.y.z version (prior to this change it used to first install the latest version, and only in a second step would it downgrade to x.y.z; this was causing issues when we bump the minimal Node.js version we support, as running yarn set version 3.6.4 wouldn't work on Node 16).

• Prevents crashes when reading from an empty .yarnrc.yml file.

---

Configuration

📅 Schedule: 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.

👻 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.

[coderabbitai]

Important

Review skipped

Bot user detected.

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

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

• 🔍 Trigger a full review

---

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

[ErisDS]

🤖 Velo CI Failure Analysis

Classification: 🔴 HARD FAIL

• Workflow: Local E2E Tests
• Failed Step: Setting up Ghost instance
• Run: View failed run
  What failed: Failed to install Ghost instance due to Corepack not being enabled
  Why: The logs indicate that the project is meant to be used with Corepack, a tool included by default with recent Node.js versions. However, Corepack is not currently enabled, which is causing the installation process to fail. This is an infrastructure issue, not a code problem.
  Action:
  The developer should enable Corepack by running corepack enable in their terminal, as suggested in the logs. This should resolve the issue and allow the Ghost instance to be installed successfully.

[ErisDS]

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

• Workflow: Local E2E Tests
• Failed Step: Setting up Ghost instance
• Run: View failed run
  What failed: CI failure - likely code issue
  Why: The failure appears to be related to code changes. Check the error output for details.
  Action:
  Review the error logs and fix the issue in your code.

[ErisDS]

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

• Workflow: Local E2E Tests
• Failed Step: Setting up Ghost instance
• Run: View failed run
  What failed: CI failure - likely code issue
  Why: The failure appears to be related to code changes. Check the error output for details.
  Action:
  Review the error logs and fix the issue in your code.

[ErisDS]

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

• Workflow: Local E2E Tests
• Failed Step: Setting up Ghost instance
• Run: View failed run
  What failed: CI failure - likely code issue
  Why: The failure appears to be related to code changes. Check the error output for details.
  Action:
  Review the error logs and fix the issue in your code.

[ErisDS]

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

• Workflow: Local E2E Tests
• Failed Step: Setting up Ghost instance
• Run: View failed run
  What failed: CI failure - likely code issue
  Why: The failure appears to be related to code changes. Check the error output for details.
  Action:
  Review the error logs and fix the issue in your code.

[ErisDS]

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

• Workflow: Local E2E Tests
• Failed Step: Setting up Ghost instance
• Run: View failed run
  What failed: CI failure - likely code issue
  Why: The failure appears to be related to code changes. Check the error output for details.
  Action:
  Review the error logs and fix the issue in your code.

[ErisDS]

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

• Workflow: Local E2E Tests
• Failed Step: Setting up Ghost instance
• Run: View failed run
  What failed: CI failure - likely code issue
  Why: The failure appears to be related to code changes. Check the error output for details.
  Action:
  Review the error logs and fix the issue in your code.

[ErisDS]

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

• Workflow: Local E2E Tests
• Failed Step: Setting up Ghost instance
• Run: View failed run
  What failed: CI failure - likely code issue
  Why: The failure appears to be related to code changes. Check the error output for details.
  Action:
  Review the error logs and fix the issue in your code.

[ErisDS]

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

• Workflow: Unit Tests
• Failed Step: Run yarn test
• Run: View failed run
  What failed: CI failure - likely code issue
  Why: The failure appears to be related to code changes. Check the error output for details.
  Action:
  Review the error logs and fix the issue in your code.