Internet Explorer is no longer supported. Many things will still work, but your experience will be degraded and some things won't function. Please use a modern browser such as Edge, Chrome, or Firefox.
This page details the changes in each maintenance release, many of which will link to our Public Issue Tracker, which you may also use to find more details or see about upcoming changes.
IssueVersionTitle
PG-3187
2025.17
FIX: PyPI simple JSON API incorrectly lists packages as yanked
PG-3172
2025.17
Add support for setting Debian package component during API/pgutil upload
PG-3168
2025.17
Allow Retention Policies to run on Edge Nodes
PG-3185
2025.17
FIX: Reopening SCA issues may error with syntax error [PostgreSQL]
PG-3183
2025.17
Use Compact API Info Endpoint on Rubygems Connector when available
PG-3184
2025.17
Add Impacted Feed Packages & Builds to Vulnerability Details [2026 Preview]
PG-3182
2025.17
FIX: Cargo manifests with a dependency that does not specify a value for `default_features` may return the wrong value.
PG-3181
2025.17
Add paging for asset items in folders with over 1000 items
PG-3180
2025.17
FIX: Vulnerability Database Updater may not update affected packages for differently-cased names [SQLServer]
PG-3179
2025.17
FIX: Performance of vulnerability overview page [PostgreSQL]
PG-3177
2025.17
FIX: Cargo crates with 1- and 2- letter names errors in UI, index
PG-3178
2025.17
FIX: Import docker images from certain Nexus registries may error with an ArgumentOutOfRange exception
PG-3176
2025.17
FIX: Add back support for API_Key as JSON property or form element [PG-3120 regression]
PG-3175
2025.17
Don't drop database objects associated with extensions on schema upgrade [PostgreSQL]
PG-3174
2025.17
FIX: Change stale Task Runner check to only run `includeTaskRunners` query string is true
PG-3173
2025.17
Add support for metadata download (PEP-658) on PyPI feeds