chore(deps): update dependency @wayofdev/commitlint-config to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@wayofdev/commitlint-config (source)	^3.0.1 → ^4.0.0

---

Release Notes

wayofdev/npm-shareable-configs (@​wayofdev/commitlint-config)

v4.0.0

Compare Source

Patch Changes

• Updated dependencies [629e9af]:
  • @​wayofdev/lint-staged-config@​2.2.0

v3.0.5

Compare Source

Patch Changes

• #​521 7b77b8d Thanks @​igomur! - Update all to latest (stylelint 15->16)

• Updated dependencies [7b77b8d]:

  • @​wayofdev/lint-staged-config@​2.1.5

v3.0.4

Compare Source

Patch Changes

• #​504 faf28ba Thanks @​igomur! - Update labeler and gh actions

• Updated dependencies [faf28ba]:

  • @​wayofdev/lint-staged-config@​2.1.4

v3.0.3

Compare Source

Patch Changes

• #​394 c2d3dac Thanks @​igomur! - chore: update versions

• Updated dependencies [c2d3dac]:

  • @​wayofdev/lint-staged-config@​2.1.3

v3.0.2

Compare Source

Patch Changes

• #​313 dfdc246 Thanks @​lotyp! - feat: update deps

• Updated dependencies [dfdc246]:

  • @​wayofdev/lint-staged-config@​2.1.2

---

Configuration

📅 Schedule: (UTC)

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

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Scope: all 8 workspace projects
Progress: resolved 0, reused 1, downloaded 0, added 0
packages/google-tag-manager              |  WARN  deprecated @types/gapi.client.tagmanager@2.0.4
Progress: resolved 175, reused 174, downloaded 0, added 0
Progress: resolved 393, reused 358, downloaded 0, added 0
Progress: resolved 582, reused 547, downloaded 0, added 0
Progress: resolved 742, reused 666, downloaded 0, added 0
Progress: resolved 1059, reused 967, downloaded 1, added 0
Progress: resolved 1509, reused 1406, downloaded 1, added 0
Progress: resolved 2061, reused 1961, downloaded 3, added 0
Progress: resolved 2413, reused 2315, downloaded 3, added 0
Progress: resolved 2431, reused 2333, downloaded 3, added 0
Progress: resolved 2468, reused 2370, downloaded 3, added 0
Progress: resolved 2468, reused 2370, downloaded 3, added 0, done
 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies

.
└─┬ @wayofdev/commitlint-config 4.0.0
  └── ✕ unmet peer @wayofdev/lint-staged-config@^2.2.0: found 2.1.1

hint: If you don't want pnpm to fail on peer dependency issues, add "strict-peer-dependencies=false" to an .npmrc file at the root of your project.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
next-starter-tpl-docs	❌ Failed (Inspect)			Apr 17, 2024 0:37am
next-starter-tpl-storybook	❌ Failed (Inspect)			Apr 17, 2024 0:37am
next-starter-tpl-web	❌ Failed (Inspect)			Apr 17, 2024 0:37am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 536e7f7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Important

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

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

(node:2111) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)