All new code requires tests to ensure against regressions.
However, if your PR contains zero code changes, feel free to select the checkmark below to indicate so.
[ ] Have you ran tests against this code?
[ ] This PR contains zero code changes.
Description of the Change
Previously, the backend would use the name of the repository for the initial name availability check, as well as would use this later on when checking that publication was successful.
But the repo name is under no obligation to match the name of the package, and in the cases where it doesn't this logic quickly breaks down, to not properly determining if the actual package name is available, as well as will fail on checking if the package was successfully published
Requirements
Filling out the template is required.
All new code requires tests to ensure against regressions.
[ ] Have you ran tests against this code?
[ ] This PR contains zero code changes.
Description of the Change
Previously, the backend would use the name of the repository for the initial name availability check, as well as would use this later on when checking that publication was successful.
But the repo name is under no obligation to match the name of the package, and in the cases where it doesn't this logic quickly breaks down, to not properly determining if the actual package name is available, as well as will fail on checking if the package was successfully published