QuickCorp / QuickCorp/QCObjects-SDK
`latest` dist-tag points to incompatible version
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
qcobjects-sdk: latest tag points to incompatible version
Repo: https://github.com/QCObjects/qcobjects-sdk
Problem
The latest npm dist-tag for qcobjects-sdk is 2.4.66, but qcobjects-cli@2.5.155 requires qcobjects-sdk@>=2.5.101-beta as a peer dependency.
The 2.5.105-beta version exists but is tagged as v2.5-beta, not latest. Since npm's default resolver only finds versions under the latest tag (and 2.4.66 < 2.5.101-beta), resolution fails with:
No matching version found for qcobjects-sdk@>=2.5.101-beta
Fix
Either:
- Promote
2.5.105-betatolatest—npm dist-tag add qcobjects-sdk@2.5.105-beta latest - Publish a stable
2.5.xrelease (drop-beta) and tag itlatest
Impact
Broken peer dependency resolution for qcobjects-cli on npm >=10. Users must manually install qcobjects-sdk@2.5.105-beta before installing the CLI.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking the npm dist-tags and published versions for qcobjects-sdk, especially latest, v2.5-beta, 2.4.66, and 2.5.105-beta. Confirm the qcobjects-cli peer dependency requirement and verify that npm can resolve it after the selected release or tag change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 58/100