siroc
siroc copied to clipboard
chore(deps): pin dependencies
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 |
||||
| release-it | devDependencies | minor | 14.11.5 -> 14.14.3 |
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
- Remove
.onlytest (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
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
- 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
tagMatchto 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
inquirerfrom 8.2.2 to 8.2.0 to avoid dropping Node 10 support (#887) (2a9a31c)
v14.14.0
- Update dependencies (
c61c780) - Minor edits to new gitlab milestones feature (
63869b8) - Add
gitlab.milestonesoption to associate milestones with a release (#883) (af0882f) - More consistently use example.org in docs, links and even tests (
3ccdef0) - Clarify the
github.hostconfig option (#875) (6d7c3f2)
v14.13.1
- Take
latestTagfrom config context (allowing any value) (9fe82ed) - Saleor project was moved to dedicated GitHub organization (#873) (
1e0f8f7)
v14.13.0
- 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
- 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
- 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
- Update dependencies (
d464518)
v14.12.2
- Add warning when
github.webandgithub.assetsare both set (closes #836) (9e72c16) - Don't return nock interceptor (
616525f) - Explain
tagNameprefix 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
v14.12.0
- Update example projects (
b500aac) - Add support for pre-releases in
runTaskstest helper (b73770e) - Remove unused argument from
getIncrement(test helper) (93b0a74) - Print
--release-versionafter incremented version is resolved (5b04ba5) - Update dependencies (
fb73af2) - Add
node-redisto example projects (069a65f) - Add test for GitHub enterprise host web release url (
e4718b0) - Wrap up the
github.autoGeneratefeature (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
- Update some dependencies (
67d0709) - Revert "unused" argument (fixes https://github.com/release-it/conventional-changelog/issues/38) (
824558f)
v14.11.7
- Quote sha with caret (fixes #801) (
fc0379c) - Defensive prop reading (
56033ca) - Add test for custom release notes command (related to #830) (
cd77539) - Remove unused argument in changelog method calls (
f31868e) - Add section "Publish to private registry" (closes #824) (
deb7c9a) - Fix Example Projects list (#827) (
3edbb23)
v14.11.6
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.
[!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.yamlfile in this repository. To trigger a single review, invoke the@coderabbitai reviewcommand.You can disable this status message by setting the
reviews.review_statustofalsein 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
@coderabbitaiin 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
@coderabbitaiin 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 pauseto pause the reviews on a PR.@coderabbitai resumeto resume the paused reviews.@coderabbitai reviewto trigger an incremental review. This is useful when automatic reviews are disabled for the repository.@coderabbitai full reviewto do a full review from scratch and review all the files again.@coderabbitai summaryto regenerate the summary of the PR.@coderabbitai generate docstringsto generate docstrings for this PR. (Beta)@coderabbitai resolveresolve all the CodeRabbit review comments.@coderabbitai configurationto show the current CodeRabbit configuration for the repository.@coderabbitai helpto get help.
Other keywords and placeholders
- Add
@coderabbitai ignoreanywhere in the PR description to prevent this PR from being reviewed. - Add
@coderabbitai summaryto generate the high-level summary at a specific location in the PR description. - Add
@coderabbitaianywhere in the PR title to generate the title automatically.
CodeRabbit Configuration File (.coderabbit.yaml)
- You can programmatically configure CodeRabbit by adding a
.coderabbit.yamlfile 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.
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 |
🚨 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 | Note | Source | CI |
|---|---|---|---|---|
| Critical CVE | npm/[email protected] |
| ⚠︎ | |
| Critical CVE | npm/[email protected] |
| ⚠︎ |
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
@SocketSecurity ignore npm/[email protected]