siroc icon indicating copy to clipboard operation
siroc copied to clipboard

chore(deps): pin dependencies

Open renovate[bot] opened this issue 1 year ago • 3 comments

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
@release-it/conventional-changelog devDependencies pin ^3.3.0 -> 3.3.0 age adoption passing confidence
release-it devDependencies minor 14.11.5 -> 14.14.3 age adoption passing confidence

Add the preset :preserveSemverRanges to your config if you don't want to pin your dependencies.


Release Notes

release-it/release-it (release-it)

v14.14.3

Compare Source

  • Remove .only test (dd249c6)
  • Temporarily(?) ignore docs.gihub.com links (returning 403) (ec3e4db)
  • Improve docs re. git.tagMatch (93c583c)
  • Replace "resources" at the bottom with link to license, order examples (e9c6b8d)
  • Update docs.github.com links (2fe93fd)
  • Add test for git.tagMatch + changelog behavior (5e843f1)
  • Improve documentatiion, mainly re. git.tagMatch (751e171)
  • Remove xlink namespace from svg (9ce7501)
  • Remove duplicate test and wrap up proxy fix (f1e8843)
  • Fixes github.proxy not working (#​863) (#​893) (1fe1afa)

v14.14.2

Compare Source

NOTE This is the latest release still supporting Node.js v10. Major issues reported in release-it v14 might still receive bug fixes and patch releases, but no new features.

v14.14.1

Compare Source

  • Update dependencies (still supporting Node.js v10) (7018194)
  • Add note about using Inquirer.js in hooks (closes #​821) (2f10cc4)
  • Add comment re. quoting CLI hook arguments (closes #​865) (ea11a0d)
  • Also transfer tagMatch to release plugins (fixes #​885) (0e0ad33)
  • Downgrade mock-fs and install polyfill for Promise.allSettled (to support Node v10) (56f1ec7)
  • test: fix CI test for different Node versions (#​888) (e8a57cc)
  • chore(deps): downgrade inquirer from 8.2.2 to 8.2.0 to avoid dropping Node 10 support (#​887) (2a9a31c)

v14.14.0

Compare Source

  • Update dependencies (c61c780)
  • Minor edits to new gitlab milestones feature (63869b8)
  • Add gitlab.milestones option to associate milestones with a release (#​883) (af0882f)
  • More consistently use example.org in docs, links and even tests (3ccdef0)
  • Clarify the github.host config option (#​875) (6d7c3f2)

v14.13.1

Compare Source

  • Take latestTag from config context (allowing any value) (9fe82ed)
  • Saleor project was moved to dedicated GitHub organization (#​873) (1e0f8f7)

v14.13.0

Compare Source

  • Allow wildcards for required branch(es) (closes #​877) (fb8622b)
  • Fix/add tests and wrap up npm.allowSameVersion (739f6f6)
  • Allow running npm version with arg --allow-same-version (#​878) (2a7565d)

v14.12.5

Compare Source

  • Fix body when auto-generating release notes (and updating) GitHub releases (2c42a8e)
  • Fix spec for different version of Git (c20d9d0)
  • Remove deprecated ref from docs (5e0d4c0)

v14.12.4

Compare Source

  • Update node-fetch (security issue in transitive dep, closes #​862) (d9aaa6c)
  • Remove the unused deprecated feature itself (d80beaf)
  • Remove old code coverage stuff (bdf6d18)

v14.12.3

Compare Source

v14.12.2

Compare Source

  • Add warning when github.web and github.assets are both set (closes #​836) (9e72c16)
  • Don't return nock interceptor (616525f)
  • Explain tagName prefix better (closes #​848) (f9d1b17)
  • Use empty string (not null) for release notes body in GitHub release request (fixes ##​855) (bdbc2ca)
  • fix spelling on git documentation (#​854) (66c6f3b)
  • Added comment about pre-release bumps (e.g. preminor) (aa34389)

v14.12.1

Compare Source

  • Fix tests on Linux (6495d3d)
  • Add latestVersion argument to getChangelog in test helper (d0ec1bb)

v14.12.0

Compare Source

  • Update example projects (b500aac)
  • Add support for pre-releases in runTasks test helper (b73770e)
  • Remove unused argument from getIncrement (test helper) (93b0a74)
  • Print --release-version after incremented version is resolved (5b04ba5)
  • Update dependencies (fb73af2)
  • Add node-redis to example projects (069a65f)
  • Add test for GitHub enterprise host web release url (e4718b0)
  • Wrap up the github.autoGenerate feature (a467b5f)
  • Update README.md (#​853) (0a4c605)
  • support github's auto generated release notes (#​843) (b612ce7)
  • feat : add a host info when generating web url (#​828) (1b1034c)

v14.11.8

Compare Source

v14.11.7

Compare Source

v14.11.6

Compare Source

  • Update dependencies (9a1d34b)
  • Fix tag name in github web release fallback url (14fcad0)
  • Changed git docs with correct hook (#​804) (588d776)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "before 4am on Monday" (UTC).

🚦 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[bot] avatar Sep 30 '24 02:09 renovate[bot]

[!IMPORTANT]

Review skipped

Ignore keyword(s) in the title.

:no_entry: Ignored keywords (1)
  • chore(deps)

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. 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.

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.

coderabbitai[bot] avatar Sep 30 '24 02:09 coderabbitai[bot]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/[email protected] 🔁 npm/[email protected] Transitive: eval, network, shell, unsafe +379 23.7 MB webpro

View full report↗︎

socket-security[bot] avatar Sep 30 '24 02:09 socket-security[bot]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSourceCI
Critical CVE npm/[email protected] ⚠︎
Critical CVE npm/[email protected] ⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

socket-security[bot] avatar Sep 30 '24 02:09 socket-security[bot]