fix(deps): update all non-major dependencies

renovate[bot] commented 3 months ago

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
next-validations	`1.0.0-1` -> `1.0.1`
pnpm (source)	`9.1.3` -> `9.6.0`

Release Notes

pnpm/pnpm (pnpm)

### [`v9.6.0`](https://togithub.com/pnpm/pnpm/releases/tag/v9.6.0): pnpm 9.6 [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.5.0...v9.6.0) #### Minor Changes - Support specifying node version (via `pnpm.executionEnv.nodeVersion` in `package.json`) for running lifecycle scripts per each package in a workspace [#6720](https://togithub.com/pnpm/pnpm/issues/6720). - Overrides now support the [`catalogs:` protocol](https://pnpm.io/catalogs) [#8303](https://togithub.com/pnpm/pnpm/issues/8303). #### Patch Changes - The `pnpm deploy` command now supports the [`catalog:` protocol](https://pnpm.io/catalogs) [#8298](https://togithub.com/pnpm/pnpm/pull/8298). - The `pnpm outdated` command now supports the [`catalog:` protocol](https://pnpm.io/catalogs) [#8304](https://togithub.com/pnpm/pnpm/pull/8304). - Correct the error message when trying to run `pnpm patch` without `node_modules/.modules.yaml` [#8257](https://togithub.com/pnpm/pnpm/issues/8257). - Silent reporting fixed with the `pnpm exec` command [#7608](https://togithub.com/pnpm/pnpm/issues/7608). - Add registries information to the calculation of dlx cache hash [#8299](https://togithub.com/pnpm/pnpm/pull/8299). #### Platinum Sponsors

#### Gold Sponsors

#### Our Silver Sponsors

### [`v9.5.0`](https://togithub.com/pnpm/pnpm/compare/v9.5.0-beta.3...v9.5.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.4.0...v9.5.0) ### [`v9.4.0`](https://togithub.com/pnpm/pnpm/compare/v9.3.0...v9.4.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.3.0...v9.4.0) ### [`v9.3.0`](https://togithub.com/pnpm/pnpm/releases/tag/v9.3.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.2.0...v9.3.0) #### Minor Changes - **Semi-breaking.** Dependency key names in the lockfile are shortened if they are longer than 1000 characters. We don't expect this change to affect many users. Affected users most probably can't run install successfully at the moment. This change is required to fix some edge cases in which installation fails with an out-of-memory error or "Invalid string length (RangeError: Invalid string length)" error. The max allowed length of the dependency key can be controlled with the `peers-suffix-max-length` setting [#8177](https://togithub.com/pnpm/pnpm/pull/8177). #### Patch Changes - Set `reporter-hide-prefix` to `true` by default for `pnpm exec`. In order to show prefix, the user now has to explicitly set `reporter-hide-prefix=false` [#8174](https://togithub.com/pnpm/pnpm/issues/8174). #### Platinum Sponsors

#### Gold Sponsors

#### Our Silver Sponsors

### [`v9.2.0`](https://togithub.com/pnpm/pnpm/releases/tag/v9.2.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.1.4...v9.2.0) #### Minor Changes - If `package-manager-strict-version` is set to `true`, pnpm will fail if its version doesn't exactly match the version in the "packageManager" field of `package.json`. #### Patch Changes - Update `@yarnpkg/pnp` to the latest version, fixing issue with `node:` imports [#8161](https://togithub.com/pnpm/pnpm/issues/8161). - Deduplicate bin names to prevent race condition and corrupted bin scripts [#7833](https://togithub.com/pnpm/pnpm/issues/7833). - pnpm doesn't fail if its version doesn't match the one specified in the "packageManager" field of `package.json` [#8087](https://togithub.com/pnpm/pnpm/issues/8087). - `exec` now also streams prefixed output when `--recursive` or `--parallel` is specified just as `run` does [#8065](https://togithub.com/pnpm/pnpm/issues/8065). #### Platinum Sponsors

#### Gold Sponsors

#### Our Silver Sponsors

### [`v9.1.4`](https://togithub.com/pnpm/pnpm/compare/v9.1.3...v9.1.4) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.1.3...v9.1.4)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

vercel[bot] commented 3 months ago

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

Name	Status	Preview	Comments	Updated (UTC)
next-validations	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 22, 2024 2:11pm
next-validations-demo	❌ Failed (Inspect)			Jul 22, 2024 2:11pm

changeset-bot[bot] commented 3 months ago

⚠️ No Changeset found

Latest commit: 0bcf4ee821c25536c547876189a8a6788cd7ea9b

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.

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[bot] commented 3 months ago

[!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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `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.` - `@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 as 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 resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

socket-security[bot] commented 3 months ago

🚨 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
Install scripts	npm/core-js-pure@3.37.1	Install script: postinstall Source: `node -e "try{require('./postinstall')}catch(e){}"`	orphan: npm/core-js-pure@3.37.1	🚫
Install scripts	npm/cypress@13.13.1	Install script: postinstall Source: `node index.js --exec install`	orphan: npm/cypress@13.13.1	🚫

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

@SocketSecurity ignore npm/core-js-pure@3.37.1
@SocketSecurity ignore npm/cypress@13.13.1

jellydn / next-validations