bytecodealliance / bytecodealliance/SIG-Registries
Consider how to handle "tombstoning" of deleted packages/releases
Open
- Dominant language
- No language data
- Stars
- 11
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Comment from user stories doc:
> @ricochet:
> If someone submits "microsoft/vscode" v1.0.0, and is not microsoft, then sue/deletion happens and that content-hash as well as name/version are tombstoned. Now what happens if microsoft wants to create a vscode package at v1.0.0? Can they? Is this a potential user story?
> @lann:
> One approach would be to permit ownership changes on names, but not permit any sort of "auto-update" between versions published by different owners.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.