You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What's the problem this feature will solve?
Currently, only URLs specified via Project-URL are verified (as part of the work for #8635).
However, the Home-page and Download-URL URLs are not verified. These are currently stored in the backend inside the Release object as plainstrings, as opposed to the URLs from Project-URL which have their own type (ReleaseURL) and are stored in their own table along with their verification status.
Since these two URLs are not verified, they are always returned as unverified (via #16531).
Describe the solution you'd like
We can change the backend so that these two URLs are verified during upload, and their verification status is stored, similar to what we do for URLs in Project-URL fields.
Part of me wonders if we should just store these as ReleaseURLs on upload and stop special-casing the metadata fields... but I think that would probably complicate things when we return project_urls in the API results.
What's the problem this feature will solve?
Currently, only URLs specified via
Project-URL
are verified (as part of the work for #8635).However, the
Home-page
andDownload-URL
URLs are not verified. These are currently stored in the backend inside theRelease
object as plain strings, as opposed to the URLs fromProject-URL
which have their own type (ReleaseURL
) and are stored in their own table along with their verification status.Since these two URLs are not verified, they are always returned as unverified (via #16531).
Describe the solution you'd like
We can change the backend so that these two URLs are verified during upload, and their verification status is stored, similar to what we do for URLs in
Project-URL
fields./cc @di @woodruffw
The text was updated successfully, but these errors were encountered: