purescript / purescript/pursuit
No ownership check on publishing repos on pursuit.
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 174
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
I have forked TinkerTravel/purescript-modules and renamed repo, but forgot to change “name” in bower.json.
so i made pulp release and new release was made but for original module, see https://pursuit.purescript.org/packages/purescript-modules/4.0.0
I have no permission over TinkerTravel/purescript-modules so probably there is some bug in ownership check in pursuit
This is actual last version of the ps-modules https://pursuit.purescript.org/packages/purescript-modules/3.0.0
besides removing 4.0.0 version release of the purescript-modules, check for ownership or write access to repo should be checked to prevent this.
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 tracing how a pulp release using the repository name from bower.json is accepted and published in Pursuit. Reproduce the ownership mismatch described for purescript-modules, then verify that releases require repository ownership or write access and that the incorrect 4.0.0 release can be removed.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100