Skip to content

Update Minor updates (minor) #132

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

Update Minor updates (minor) #132

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 12, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@rushstack/eslint-plugin-security (source) ^0.8.3 -> ^0.10.0 age adoption passing confidence
chrono-node@<2.2.4 >=2.7.7 -> >=2.8.0 age adoption passing confidence
lint-staged ^15.4.3 -> ^15.5.1 age adoption passing confidence
npm@>=7.9.0 <8.11.0 (source) [>=8.11.0 -> >=8.19.4](https://renovatebot.com/diffs/npm/npm@&gt;&#x3D;7.9.0 <8.11.0/8.11.0/8.19.4) age adoption passing confidence
pnpm (source) 10.2.1 -> 10.10.0 age adoption passing confidence
semver@>=7.0.0 <7.5.2 [>=7.5.2 -> >=7.7.1](https://renovatebot.com/diffs/npm/semver@&gt;&#x3D;7.0.0 <7.5.2/7.5.2/7.7.1) age adoption passing confidence
sort-package-json ^2.14.0 -> ^2.15.1 age adoption passing confidence
taze ^18.4.0 -> ^18.7.1 age adoption passing confidence
typedoc-plugin-markdown (source) 4.4.2 -> 4.6.3 age adoption passing confidence

Release Notes

microsoft/rushstack (@​rushstack/eslint-plugin-security)

v0.10.0

Compare Source

Tue, 11 Mar 2025 02:12:33 GMT

Minor changes
  • Bump the @typescript-eslint/* packages to add support for TypeScript 5.8.

v0.9.0

Compare Source

Sat, 01 Mar 2025 07:23:16 GMT

Minor changes
  • Bump the @typescript-eslint/* dependencies to ~8.24.0 to support newer versions of TypeScript.
wanasit/chrono (chrono-node@<2.2.4)

v2.8.0

Compare Source

New/Fix: Reference date calculation on the assigned timezone 4033a27

Previously, the reference date calculation (e.g., "1 day ago", "tomorrow at 9am") was based on the interpretation of the reference instant/timestamp using the system timezone rather than the assigned timezone (e.g., "April 5" in the system timezone may already "April 6" in the assigned timezone).

const refInstant = new Date("2025-02-27T22:00:00.000Z");
// This instant/timestamp
// = Thu Feb 27 2025 15:00:00 GMT-0800 (PST)
// = Fri Feb 28 2025 08:00:00 GMT+0900 (JST)

chrono.parseDate("Tomorrow at 9am", { instant: refInstant, timezone: "PST" })
// In PST, "Tomorrow at 9am" => Fri Feb 28 2025 09:00:00 GMT-0800 (PST)

chrono.parseDate("Tomorrow at 9am", { instant: refInstant, timezone: "JST" })
// In JST, "Tomorrow at 9am" => Sat Mar 1 2025 09:00:00 GMT+0900 (JST)

This changed some current relative date/time output. So, it is published in a minor version, instead of a patch.

v2.7.9

Compare Source

  • New: Italian (IT) support (beta/untested).
  • New: (en) add "Overmorrow" support in casual date e1acb29
  • Fix: (jp) rewrite 当日 to 本日
  • Fix: timezone option for relative dates should affect time 8c415a8

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
lint-staged/lint-staged (lint-staged)

v15.5.1

Compare Source

Patch Changes

  • #​1533 5d53534 Thanks @​iiroj! - Improve listing of staged files so that lint-staged doesn't crash when encountering an uninitialized submodule. This should result in less errors like:

    ✖ Failed to get staged files!

v15.5.0

Compare Source

Minor Changes
  • #​1526 630af5f Thanks @​iiroj! - Lint-staged no longer resets to the original state when preventing an empty git commit. This happens when your configured tasks reset all the staged changes, typically when trying to commit formatting changes which conflict with your linter setup like ESLint or Prettier.
Example with Prettier

By default Prettier prefers double quotes.

Previously
  1. Stage file.js with only double quotes " changed to '
  2. Run git commit -am "I don't like double quotes"
  3. Lint-staged runs prettier --write file.js, converting all the ' back to "
  4. Because there are now no changes, lint-staged fails, cancels the commit, and resets back to the original state
  5. Commit was not done, original state is restored and single quotes ' are staged
Now
  1. Stage file.js with only double-quotes " changed to '
  2. Run git commit -am "I don't like double quotes"
  3. Lint-staged runs prettier --write file.js, converting all the ' back to "
  4. Because there are now no changes, lint-staged fails and cancels the commit
  5. Commit was not done, and there are no staged changes
npm/cli (npm@>=7.9.0 <8.11.0)

v8.19.4

Compare Source

Documentation
Dependencies

v8.19.3

Compare Source

Bug Fixes
Documentation
Dependencies

v8.19.2

Compare Source

Dependencies

v8.19.1

Compare Source

Bug Fixes

v8.19.0

Compare Source

Features
Bug Fixes
Documentation
Dependencies

v8.18.0

Compare Source

v8.18.0 (2022-08-17)

Features
Bug Fixes
Documentation
Dependencies

v8.17.0

Compare Source

v8.17.0 (2022-08-10)

Features
Bug Fixes
Documentation
Dependencies

v8.16.0

Compare Source

v8.16.0 (2022-08-03)

Features
Bug Fixes
Documentation
Dependencies

v8.15.1

Compare Source

v8.15.1 (2022-07-27)

Bug Fixes
Documentation
Dependencies

v8.15.0

Compare Source

v8.15.0 (2022-07-20)

Features
Bug Fixes
Documentation
Dependencies

v8.14.0

Compare Source

v8.14.0 (2022-07-13)

Features
Bug Fixes
Documentation
Dependencies

v8.13.2

Compare Source

v8.13.2 (2022-06-29)

Documentation
Dependencies

v8.13.1

Compare Source

v8.13.1 (2022-06-23)

Dependencies

v8.13.0

Compare Source

v8.13.0 (2022-06-22)

Features
Bug Fixes
Documentation
Dependencies

v8.12.2

Compare Source

v8.12.2 (2022-06-15)

Dependencies

v8.12.1

Compare Source

v8.12.1 (2022-06-02)

Bug Fixes

v8.12.0

Compare Source

v8.12.0 (2022-06-01)

Features
Bug Fixes
Dependencies
pnpm/pnpm (pnpm)

v10.10.0

Compare Source

Minor Changes
  • Allow loading the preResolution, importPackage, and fetchers hooks from local pnpmfile.
Patch Changes
  • Fix cd command, when shellEmulator is true #​7838.
  • Sort keys in pnpm-workspace.yaml #​9453.
  • Pass the npm_package_json environment variable to the executed scripts #​9452.
  • Fixed a mistake in the description of the --reporter=silent option.

v10.9.0

Compare Source

Minor Changes

  • Added support for installing JSR packages. You can now install JSR packages using the following syntax:

    pnpm add jsr:<pkg_name>

    or with a version range:

    pnpm add jsr:<pkg_name>@&#8203;<range>

    For example, running:

    pnpm add jsr:@&#8203;foo/bar

    will add the following entry to your package.json:

    {
  "dependencies": {
    "@&#8203;foo/bar": "jsr:^0.1.2"
  }
}

    When publishing, this entry will be transformed into a format compatible with npm, older versions of Yarn, and previous pnpm versions:

    {
  "dependencies": {
    "@&#8203;foo/bar": "npm:@&#8203;jsr/foo__bar@^0.1.2"
  }
}

    Related issue: #​8941.

    Note: The @jsr scope defaults to https://npm.jsr.io/ if the @jsr:registry setting is not defined.

  • Added a new setting, dangerouslyAllowAllBuilds, for automatically running any scripts of dependencies without the need to approve any builds. It was already possible to allow all builds by adding this to pnpm-workspace.yaml:

    neverBuiltDependencies: []

    dangerouslyAllowAllBuilds has the same effect but also allows to be set globally via:

    pnpm config set dangerouslyAllowAllBuilds true

    It can also be set when running a command:

    pnpm install --dangerously-allow-all-builds
Patch Changes
  • Fix a false negative in verifyDepsBeforeRun when nodeLinker is hoisted and there is a workspace package without dependencies and node_modules directory #​9424.
  • Explicitly drop verifyDepsBeforeRun support for nodeLinker: pnp. Combining verifyDepsBeforeRun and nodeLinker: pnp will now print a warning.

v10.8.1

Compare Source

Patch Changes
  • Removed bright white highlighting, which didn't look good on some light themes #​9389.
  • If there is no pnpm related configuration in package.json, onlyBuiltDependencies will be written to pnpm-workspace.yaml file #​9404.

v10.8.0

Compare Source

Minor Changes

  • Experimental. A new hook is supported for updating configuration settings. The hook can be provided via .pnpmfile.cjs. For example:

    module.exports = {
  hooks: {
    updateConfig: (config) => ({
      ...config,
      nodeLinker: "hoisted",
    }),
  },
};

  • Now you can use the pnpm add command with the --config flag to install new configurational dependencies #​9377.

Patch Changes
  • Do not hang indefinitely, when there is a glob that s

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.

@renovate renovate bot requested a review from prisis as a code owner February 12, 2025 14:35
@renovate renovate bot added the c: dependencies Pull requests that adds/updates a dependency label Feb 12, 2025
@renovate renovate bot enabled auto-merge (squash) February 12, 2025 14:35
@coderabbitai coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 12, 2025 •
edited
Loading

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.

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

Support

Need help? Join our Discord community for assistance with any issues or questions.

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 sequence diagram to generate a sequence diagram of the changes in this PR.
  • @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 GitHub Actions
Copy link
Contributor

github-actions bot commented Feb 12, 2025 •
edited
Loading

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 Minor updates (minor)". 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

@pkg-pr-new pkg.pr.new
Copy link

pkg-pr-new bot commented Feb 12, 2025 •
edited
Loading

Open in Stackblitz

@anolilab/multi-semantic-release

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

@anolilab/rc

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

@anolilab/semantic-release-preset

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

@anolilab/semantic-release-pnpm

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

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

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

commit: 8f10201

@codecov Codecov
Copy link

codecov bot commented Feb 12, 2025 •
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.31%. Comparing base (edf108c) to head (8f10201).
Report is 5 commits behind head on main.

Additional details and impacted files 
@@             Coverage Diff             @@
##             main     #132       +/-   ##
===========================================
+ Coverage   65.13%   88.31%   +23.18%     
===========================================
  Files          32       10       -22     
  Lines         803      308      -495     
  Branches      114       50       -64     
===========================================
- Hits          523      272      -251     
+ Misses        280       36      -244
Flag Coverage Δ
rc 92.17% <ø> (ø)
semantic-release-clean-package-json 86.01% <ø> (ø)
semantic-release-pnpm ?

see 22 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@renovate renovate bot force-pushed the renovate/minor-updates branch 2 times, most recently from 7994650 to 282f7ec Compare February 17, 2025 11:32
@socket-security Socket Security
Copy link

socket-security bot commented Feb 17, 2025 •
edited
Loading

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Addedleft-pad@​1.3.01001007778100
Updated@​rushstack/​eslint-plugin-security@​0.8.3 ⏵ 0.10.010010091 +186 +2100

View full report

@renovate renovate bot force-pushed the renovate/minor-updates branch 2 times, most recently from cef193c to 7e9c6bc Compare February 21, 2025 11:33
@renovate renovate bot force-pushed the renovate/minor-updates branch 3 times, most recently from 28a9388 to 7f2560e Compare March 4, 2025 11:43
@renovate renovate bot force-pushed the renovate/minor-updates branch 5 times, most recently from 0ec7e75 to f666c33 Compare March 17, 2025 10:40
@renovate renovate bot force-pushed the renovate/minor-updates branch 3 times, most recently from d35f694 to c41abfb Compare March 24, 2025 13:31
@renovate renovate bot force-pushed the renovate/minor-updates branch 2 times, most recently from 8f10201 to 779622e Compare March 31, 2025 10:37
@renovate renovate bot force-pushed the renovate/minor-updates branch 4 times, most recently from 51b3ec8 to 1471463 Compare April 11, 2025 12:43
@renovate renovate bot force-pushed the renovate/minor-updates branch from 1471463 to 6c57cd5 Compare April 14, 2025 16:43
@renovate renovate bot force-pushed the renovate/minor-updates branch 2 times, most recently from fc1fed3 to 3b26e7c Compare April 17, 2025 12:30
@renovate renovate bot force-pushed the renovate/minor-updates branch 2 times, most recently from e369b4c to d5261d1 Compare April 28, 2025 12:59
@renovate
Update Minor updates
79fe0b2 
Signed-off-by: Renovate Bot <bot@renovateapp.com>
@renovate renovate bot force-pushed the renovate/minor-updates branch from d5261d1 to 79fe0b2 Compare May 1, 2025 15:41
@prisis prisis closed this May 7, 2025
auto-merge was automatically disabled May 7, 2025 19:08

Pull request was closed

@prisis prisis deleted the renovate/minor-updates branch May 7, 2025 19:08
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Jun 6, 2025

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using our GitHub Discussions tab for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 6, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@prisis prisis Awaiting requested review from prisis prisis is a code owner

Assignees
No one assigned
Labels
c: dependencies Pull requests that adds/updates a dependency
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@prisis