Update Patch updates (patch)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
chrono-node@<2.2.4	>=2.7.7 -> >=2.7.8
cross-spawn@>=7.0.0 <7.0.5	[>=7.0.5 -> >=7.0.6](https://renovatebot.com/diffs/npm/cross-spawn@&gt;&#x3D;7.0.0 <7.0.5/7.0.5/7.0.6)
semver@>=7.0.0 <7.5.2	[>=7.5.2 -> >=7.5.4](https://renovatebot.com/diffs/npm/semver@&gt;&#x3D;7.0.0 <7.5.2/7.5.2/7.5.4)

---

Release Notes

wanasit/chrono (chrono-node@<2.2.4)

v2.7.8

Compare Source

• Fix: (en) The second could be an ordinal number or time-unit 6d8d672
• Fix: (en) Recognize "of" between month name and year 257722f
• Fix: (en) The "may" could be verb or month name a857d3f
• New: add debug tags for result/relativeDate 80c126b
• New: add debug tags for parser/SlashDateFormatParser and parser/ENTimeExpressionParser 6646c75
• New: (en) Add support for weekend/weekday mentioning 3a15d3d

moxystudio/node-cross-spawn (cross-spawn@>=7.0.0 <7.0.5)

v7.0.6

Compare Source

npm/node-semver (semver@>=7.0.0 <7.5.2)

v7.5.4

Compare Source

Bug Fixes

• cc6fde2 #​588 trim each range set before parsing (@​lukekarrys)
• 99d8287 #​583 correctly parse long build ids as valid (#​583) (@​lukekarrys)

v7.5.3

Compare Source

Bug Fixes

• abdd93d #​571 set max lengths in regex for numeric and build identifiers (#​571) (@​lukekarrys)

Documentation

• bf53dd8 #​569 add example for > comparator (#​569) (@​mbtools)

---

Configuration

📅 Schedule: Branch creation - "after 10:00 before 19:00 every weekday except after 13:00 before 14:00" in timezone Europe/Berlin, 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.

---

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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "Update Patch updates (patch)". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - build
 - chore
 - ci
 - docs
 - feat
 - fix
 - perf
 - infra
 - refactor
 - revert
 - test

[socket-security]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher

View full report↗︎

[pkg-pr-new]

Open in Stackblitz

@anolilab/multi-semantic-release

npm i https://pkg.pr.new/anolilab/semantic-release/@anolilab/multi-semantic-release@110

@anolilab/semantic-release-clean-package-json

npm i https://pkg.pr.new/anolilab/semantic-release/@anolilab/semantic-release-clean-package-json@110

@anolilab/rc

npm i https://pkg.pr.new/anolilab/semantic-release/@anolilab/rc@110

@anolilab/semantic-release-pnpm

npm i https://pkg.pr.new/anolilab/semantic-release/@anolilab/semantic-release-pnpm@110

@anolilab/semantic-release-preset

npm i https://pkg.pr.new/anolilab/semantic-release/@anolilab/semantic-release-preset@110

commit: 0a755e6

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.13%. Comparing base (edf108c) to head (0a755e6).
Report is 5 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #110   +/-   ##
=======================================
  Coverage   65.13%   65.13%           
=======================================
  Files          32       32           
  Lines         803      803           
  Branches      114      114           
=======================================
  Hits          523      523           
+ Misses        280      277    -3     
- Partials        0        3    +3     

Flag	Coverage Δ
rc	92.17% <ø> (ø)
semantic-release-clean-package-json	86.01% <ø> (ø)
semantic-release-pnpm	50.70% <ø> (ø)

see 1 file with indirect coverage changes