feat: security fix on vant package

[fengmk2]

see https://github.com/youzan/vant/releases/tag/v4.9.15

Summary by CodeRabbit

• New Features
  • Enhanced tracking of problematic versions for the vant package with new version mappings.
  • Added links to relevant release notes for affected versions.

[coderabbitai]

Walkthrough

The pull request updates the package.json file by adding comprehensive version mappings for the vant package. These mappings identify specific versions with potential issues and provide recommended upgrades. The changes cover multiple version ranges (2.x, 3.x, and 4.x), suggesting a systematic approach to tracking and mitigating potential package-related problems by directing users to newer, presumably more stable versions.

Changes

File	Change Summary
package.json	Added bug-versions entries for vant package: - Mapped problematic versions to newer releases - Covered versions 2.13.3-5, 3.6.13-15, and 4.9.11-14 - Provided GitHub release note links for context

Poem

🐰 Hop, hop, through package versions we go,
Mapping bugs with a rabbit's keen eye so!
From old to new, we leap with delight,
Vant's versions now aligned just right!
Bug-free code, our warren's sweet song! 🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0da31c3 and 009d731.

📒 Files selected for processing (1)

• package.json (1 hunks)

🔇 Additional comments (1)

package.json (1)

1187-1227: LGTM! Comprehensive version mappings for security fix.

The changes systematically address the security issue across all affected versions of vant (2.x, 3.x, 4.x), with proper version mappings and documentation.

Let's verify the release notes and ensure the versions are correctly mapped:

✅ Verification successful

Security fix version mappings verified - Correct and timely updates

The version mappings in package.json are accurate and align with the security fix releases:

• The problematic versions (4.9.11-4.9.14, 3.6.13-3.6.15, 2.13.3-2.13.5) were all published on Dec 19, 2024
• The fixed versions (4.9.15, 3.6.16, 2.13.6) were published shortly after on the same day
• The dist-tags confirm these are now the latest versions for each major version:
  • latest (v4): 4.9.15
  • latest-v3: 3.6.16
  • latest-v2: 2.13.6

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the vant release notes and version information
# Fetch the release notes to verify the security fix details
curl -s -L https://github.com/youzan/vant/releases/tag/v4.9.15

# Verify if these are the latest versions available
curl -s https://registry.npmjs.org/vant | jq -r '.versions | keys[]' | sort -V | tail -n 5

Length of output: 78005

---

Script:

#!/bin/bash
# Let's try a different approach to verify the versions and security fix
# First, let's check the latest versions from npm registry for each major version
echo "Latest versions from npm:"
curl -s "https://registry.npmjs.org/vant" | jq -r '.["dist-tags"]'

# Check if these versions were published recently
echo -e "\nRecent versions and their publish dates:"
curl -s "https://registry.npmjs.org/vant" | jq -r '.time | to_entries | .[] | select(.key | contains("4.9.") or contains("3.6.") or contains("2.13.")) | "\(.key) => \(.value)"'

Length of output: 1976

---

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
• Mastodon
• Reddit
• LinkedIn

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