Skip to content

fix(plugin): honor caret ranges below 1.0.0 - #2299

Open
Whxuan0701 wants to merge 1 commit into
jackwener:mainfrom
Whxuan0701:fix/plugin-caret-zero-range
Open

fix(plugin): honor caret ranges below 1.0.0#2299
Whxuan0701 wants to merge 1 commit into
jackwener:mainfrom
Whxuan0701:fix/plugin-caret-zero-range

Conversation

@Whxuan0701

Copy link
Copy Markdown

Description

Apply standard caret compatibility bounds to pre-1.0 plugin versions:

  • keep ^1.2.0 bounded below 2.0.0
  • bound ^0.2.0 below 0.3.0
  • bound ^0.0.3 below 0.0.4

This prevents plugins from being treated as compatible across potentially breaking 0.x releases.

Related issue: N/A (independently identified)

Type of Change

  • 🐛 Bug fix
  • ✨ New feature
  • 🌐 New site adapter
  • 📝 Documentation
  • ♻️ Refactor
  • 🔧 CI / build / tooling

Checklist

  • I ran the checks relevant to this PR
  • I updated tests or docs if needed
  • I included output or screenshots when useful

Documentation (if adding/modifying an adapter)

  • Added doc page under docs/adapters/ (if new adapter)
  • Updated docs/adapters/index.md table (if new adapter)
  • Updated sidebar in docs/.vitepress/config.mts (if new adapter)
  • Updated README.md / README.zh-CN.md when command discoverability changed
  • Used positional args for the command primary subject unless a named flag is clearly better
  • Normalized expected adapter failures to CliError subclasses instead of raw Error

Screenshots / Output

npm run typecheck
> tsc --noEmit

npm run build
✅ Manifest compiled: 1331 entries

npm test
Test Files  590 passed (590)
Tests       6740 passed | 1 skipped (6741)

Risks / Known Gaps

This changes compatibility decisions only for caret ranges whose major version is zero. Other supported range forms are unchanged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant