Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow scope admins to RENAME a package #997

Open
TriMoon opened this issue Feb 28, 2025 · 0 comments
Open

Allow scope admins to RENAME a package #997

TriMoon opened this issue Feb 28, 2025 · 0 comments

Comments

@TriMoon
Copy link

TriMoon commented Feb 28, 2025

"I have been struggling to learn how JSR works"

I recently started to use JSR and started with an upload of my new package.
Like every new user i didn't know how JSR expects stuff to be done, so i used the "Try and see" method.
While trying stuff, i decided to use -rc# at end of the version as one would normally do for tests, i noticed that the intermediate "try" versions stay visible and accessible to the public, not to mention that i didn't get any feedback about the score etc anymore from the JSR site due to non-stable version.
This of-course made me heat up, because i certainly do NOT want those to be visible/accessible by the public for obvious reasons.
So... I went the route of creating a separate package with a randomly generated name, using uuidgen, so far so good right?
Well...no not really...

  1. I started with the package name that i want to use as end result.
  2. It has "Try-out-JSR functionality" versions that i want to get rid of.
  3. This package had YYYY.MM.DD versioning, which is perfectly valid for semver.
  4. The test package also has this versioning.
  5. I am almost ready to start publishing my REAL public version, but this time ofcourse using 1.0.0 as version.

So the last step that is needed is to get rid of these "old" stuff and publish my package under the name i started with...
But i can't seem to do that, because we can't delete nor rename packages...

Does this mean that JSR is not fit for developers that want to publish NEW software under a name they actually want and care for? 🤔

  • Until i am able to do what i described above i will just continue developing my software package in my GitLab repo, but not upload to JSR yet or at all if not possible.
  • https://jsr.io/@trimoon/mdmap

Related issues i've been reading: #250, #740, #899

@github-project-automation github-project-automation bot moved this to Needs Triage in JSR Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Needs Triage
Development

No branches or pull requests

1 participant