Previously published npm packages are being overwritten by the publish tool
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- release
Research direction
Start by reviewing the publish tool and the referenced commit 5f1a94967148173f78ff00792c29ef5f2a1a3edb, then compare the affected package versions listed in the issue. Reproduce the stable CI failure if possible; done means previously published packages are not overwritten and the stable pipeline builds successfully.
Written by the indexing model from the issue text.
Description
The publish tool should not be overwriting previously published packages.
https://docs.npmjs.com/policies/unpublish
Overwriting published packages is against npm's policy, and I'm not sure how this was even possible because the npm registry should be immutable.
Our stable CI pipeline has failed to build since this PR was merged
https://github.com/DefinitelyTyped/DefinitelyTyped/commit/5f1a94967148173f78ff00792c29ef5f2a1a3edb
We are using @types/react-redux 7.1.16. That npm package was originally published 9 months ago, but overwritten 6 days ago.
https://www.npmjs.com/package/@types/react-redux/v/7.1.16
I started looking into some of the other packages that would have been affected by that same PR.
https://www.npmjs.com/package/@types/chai-enzyme/v/0.6.7
https://www.npmjs.com/package/@types/emoji-mart/v/3.0.4
https://www.npmjs.com/package/@types/enzyme/v/3.10.8
All @types packages affected by the above PR have their previously published npm packages overwritten 6 days ago.
- Dominant language
- TypeScript
- Stars
- 423
- Forks
- 237
- Avg merge
- 18h 18m
- Merged PRs (30d)
- 11
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.
More from microsoft/DefinitelyTyped-tools
-
Difficulty 3/5 1-2 days Newbie friendliness 66/100
microsoft/DefinitelyTyped-tools#1324 · 7 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 32/100
microsoft/DefinitelyTyped-tools#1230 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
microsoft/DefinitelyTyped-tools#1229 ·
-
microsoft/DefinitelyTyped-tools#1218 · 1 reaction · 1 assignee ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
microsoft/DefinitelyTyped-tools#1211 · 1 comment ·
All issues in microsoft/DefinitelyTyped-tools
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
receptron/mulmoterminal#2264 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
components-web-app/docs#96 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
simonsobs/tileviewer#114 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100