[Snyk] Upgrade three from 0.161.0 to 0.162.0

[quantum9Innovation]

User description

Snyk has created this PR to upgrade three from 0.161.0 to 0.162.0.

As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.

✨ Snyk has automatically assigned this pull request, set who gets assigned.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 1 version ahead of your current version.
• The recommended version was released 23 days ago, on 2024-02-29.

Release notes

Package name: three

• 0.162.0 - 2024-02-29
• 0.161.0 - 2024-01-31

from three GitHub release notes

Commit messages

Package name: three

• ef80ac7 r162
• 9e1a30b Updated builds.
• a9747f3 Examples: Added WebXR TransformControls example (#27845)
• bafd714 TSL: Fix tslFn generate in isolated cache (#27844)
• ae1475f WebGPURenderer: Added sync render()/clear() (#27840)
• 4800ed8 VRMLLoader: Fix transparency settings for lines and points. (#27841)
• c4c01c3 WebGPURenderer: Define setAnimationLoop() as default in examples (#27839)
• 0498e27 Editor: Added Image render section (Realistic shading not ready yet).
• 71c1f51 Raycaster: Improve readability.
• 4654223 Editor: Improved Viewport.Info.
• e29ce31 WebGPURenderer: Fix call clear() before rendering (#27835)
• 89aa843 OrbitControls: fix zoom-changed detection (#27834)
• c66f9d6 3dmLoader: Updating to 8.4.0 (#27833)
• 6b50ba4 Editor: Removed VisionOS test.
• c5d243f Editor: Moved SidebarAnimation to SidebarObjectAnimation.
• 3f949bd Docs: Clean up. (#27830)
• f67234d docs: fix GridHelper hierarchy (#27817)
• 5838c86 Editor: Avoid initializing Pathtracer when moving the camera.
• 3d07bac CondNode: Fix duplicate conditional (#27828)
• d0b43f2 WGLSLNodeBuilder: Fix equals (#27826)
• a963bf7 WebGPURenderer: `getTextureLevel` of `background` should multiply `maxMipLevel` (#27820)
• f3f0586 BufferGeometry: Use dedicated `BufferAttribute` API in `computeTangents()`. (#27825)
• 5e2397a BufferGeometry: Remove outdated advice from error message. (#27824)
• 9444fc9 Updated builds.

Compare

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

👩‍💻 Set who automatically gets assigned

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

---

Type

enhancement

---

Description

• Upgraded the three library from version 0.161.0 to 0.162.0 to keep the project dependencies up-to-date and potentially leverage new features or bug fixes from the newer version.

---

Changes walkthrough

	Relevant files
Dependencies	package.json Upgrade `three` Dependency to Version `0.162.0`                    client/package.json Upgraded three dependency from version 0.161.0 to 0.162.0. +1/-1

---

✨ PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[qodo-code-review]

PR-Agent was enabled for this repository. To use it, please link your git user with your CodiumAI identity here.

PR Description updated to latest commit (deed73d)

• Copy walkthrough table to "Files Changed" Tab

[qodo-code-review]

PR-Agent was enabled for this repository. To use it, please link your git user with your CodiumAI identity here.

PR Review

⏱️ Estimated effort to review [1-5]	1, because the PR involves a simple version bump in the package.json for the 'three' library from 0.161.0 to 0.162.0. This is a straightforward change with minimal impact on the codebase, assuming no breaking changes between these versions.
🧪 Relevant tests	No
🔍 Possible issues	Dependency Compatibility: Ensure that the new version of 'three' is compatible with the current project setup and does not introduce breaking changes that could affect the build or runtime.
🔒 Security concerns	No

---

✨ Review tool usage guide:

---

Overview:
The review tool scans the PR code changes, and generates a PR review. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on any PR.
When commenting, to edit configurations related to the review tool (pr_reviewer section), use the following template:

/review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=...

With a configuration file, use the following template:

[pr_reviewer]
some_config1=...
some_config2=...

Utilizing extra instructions The review tool can be configured with extra instructions, which can be used to guide the model to a feedback tailored to the needs of your project. Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify the relevant sub-tool, and the relevant aspects of the PR that you want to emphasize. Examples for extra instructions: [pr_reviewer] # /review # extra_instructions=""" In the 'possible issues' section, emphasize the following: - Does the code logic cover relevant edge cases? - Is the code logic clear and easy to understand? - Is the code logic efficient? ... """ Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

How to enable\disable automation When you first install PR-Agent app, the default mode for the review tool is: pr_commands = ["/review", ...] meaning the review tool will run automatically on every PR, with the default configuration. Edit this field to enable/disable the tool, or to change the used configurations

Auto-labels The review tool can auto-generate two specific types of labels for a PR: a possible security issue label, that detects possible security issues (enable_review_labels_security flag) a Review effort [1-5]: x label, where x is the estimated effort to review the PR (enable_review_labels_effort flag)

Extra sub-tools The review tool provides a collection of possible feedbacks about a PR. It is recommended to review the possible options, and choose the ones relevant for your use case. Some of the feature that are disabled by default are quite useful, and should be considered for enabling. For example: require_score_review, require_soc2_ticket, require_can_be_split_review, and more.

Auto-approve PRs By invoking: /review auto_approve The tool will automatically approve the PR, and add a comment with the approval. To ensure safety, the auto-approval feature is disabled by default. To enable auto-approval, you need to actively set in a pre-defined configuration file the following: [pr_reviewer] enable_auto_approval = true (this specific flag cannot be set with a command line argument, only in the configuration file, committed to the repository) You can also enable auto-approval only if the PR meets certain requirements, such as that the estimated_review_effort is equal or below a certain threshold, by adjusting the flag: [pr_reviewer] maximal_review_effort = 5

More PR-Agent commands To invoke the PR-Agent, add a comment using one of the following commands: /review: Request a review of your Pull Request. /describe: Update the PR title and description based on the contents of the PR. /improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback. /ask <QUESTION>: Ask a question about the PR. /update_changelog: Update the changelog based on the PR's contents. /add_docs 💎: Generate docstring for new components introduced in the PR. /generate_labels 💎: Generate labels for the PR based on the PR's contents. /analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component. See the tools guide for more details. To list the possible configuration parameters, add a /config comment.

See the review usage page for a comprehensive guide on using this tool.

[qodo-code-review]

PR Code Suggestions

No code suggestions found for PR.