OpenUPM Recent Improvements, May 2026
OpenUPM shipped a set of smaller improvements between May 15 and May 17, 2026. Some were already covered separately, including UPM package signing, UnityNuGet package signing, the queue status page, and UnityNuGet search through OpenUPM. This roundup covers the remaining user-visible changes.
Package Pages
Package install commands now prefer stable releases when a package has both stable and prerelease versions. The latest prerelease command remains available, but the default path is clearer for projects that want the most recent stable package version.
Package pages also expose more maintenance context. Archived GitHub repositories now show an archived status chip, and README sections can show when the synced README content was last updated. Manual installation modal links can be opened directly, which makes support answers easier to share.
Package Authoring
Several changes focused on making package releases easier to understand and less likely to publish the wrong thing. The Builds section can now show the actual package version published by a build when that information is available, while keeping a fallback for older release records. Git-source builds now validate that the discovered package.json version matches the queued package version before publishing.
Website-only package rename redirects are now supported through package metadata, while registry package names remain unchanged so Unity projects still update dependencies explicitly. Package JSON parsing now tolerates a leading UTF-8 byte order mark, which avoids rejecting otherwise valid manifests saved by some editors. New git-source publishes also include source repository metadata in the generated package manifest.
Registry Reliability
The registry runtime has been stabilized on Verdaccio 6. That upgrade is what made the separate UnityNuGet search improvement possible, and it gives OpenUPM a current supported registry base for future work.