-
Notifications
You must be signed in to change notification settings - Fork 60
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
Setting $VERSION to an unquoted v-string results in an indexing fail for new package names #365
Comments
Weird. |
rjbs
added
bug
indexer
How we index uploads
metadata
version and metadata extraction and handling
labels
Apr 28, 2023
rjbs
added a commit
to rjbs/pause
that referenced
this issue
Apr 30, 2023
Right now, this fails weirdly. See andk#365.
I started #410 I think we can fix this once we do some other work. |
rjbs
added a commit
to rjbs/pause
that referenced
this issue
Apr 30, 2023
Right now, this fails weirdly. See andk#365.
rjbs
added a commit
to rjbs/pause
that referenced
this issue
Apr 26, 2024
Right now, this fails weirdly. See andk#365.
rjbs
added a commit
to rjbs/pause
that referenced
this issue
Apr 28, 2024
Right now, this fails weirdly. See andk#365.
rjbs
added a commit
to rjbs/pause
that referenced
this issue
Apr 28, 2024
Right now, this fails weirdly. See andk#365.
rjbs
added a commit
to rjbs/pause
that referenced
this issue
Apr 28, 2024
Right now, this fails weirdly. See andk#365.
rjbs
added a commit
to rjbs/pause
that referenced
this issue
Apr 28, 2024
Right now, this fails weirdly. See andk#365, which says: > If you're doing the first release of a package, and you set the version > string to an unquoted v-string, such as > > our $VERSION = v1.0.1; > > Then the uploader will get a message saying they don't have an indexing > permission on the package. > > Putting double quotes around the v-string will fix it, so we should at least > recognise the problem and tell the uploader.
rjbs
added a commit
to rjbs/pause
that referenced
this issue
May 12, 2024
Right now, this fails weirdly. See andk#365, which says: > If you're doing the first release of a package, and you set the version > string to an unquoted v-string, such as > > our $VERSION = v1.0.1; > > Then the uploader will get a message saying they don't have an indexing > permission on the package. > > Putting double quotes around the v-string will fix it, so we should at least > recognise the problem and tell the uploader.
rjbs
added a commit
to rjbs/pause
that referenced
this issue
May 19, 2024
Right now, this fails weirdly. See andk#365, which says: > If you're doing the first release of a package, and you set the version > string to an unquoted v-string, such as > > our $VERSION = v1.0.1; > > Then the uploader will get a message saying they don't have an indexing > permission on the package. > > Putting double quotes around the v-string will fix it, so we should at least > recognise the problem and tell the uploader.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you're doing the first release of a package, and you set the version string to an unquoted v-string, such as
Then the uploader will get a message saying they don't have an indexing permission on the package.
Putting double quotes around the v-string will fix it, so we should at least recognise the problem and tell the uploader.
The text was updated successfully, but these errors were encountered: