Deprecation of MyGet official package feeds

[glopesdev]

TL;DR

Warning

The official transition of all Bonsai packages to nuget.org is nearly complete and we will be officially deprecating and archiving the original MyGet feeds shortly after release of Bonsai 2.9. We will not remove these legacy feeds, but we will not actively package them with fresh installs of Bonsai (i.e. existing installations and local environments will still be able to access them). If you are a maintainer of community packages, please reach out to us if you haven't migrated your packages.

Motivation

Following the major outage discussed at #1500 we have investigated the future of MyGet, both by attempts to directly reach out to support, and via following up on public reports of similar issues across the MyGet ecosystem (see 1, 2). To put it mildly, the conclusions are not encouraging, and we have to move on.

Further to the risk of future outages or outright deletion, the old feeds at myget.org/bonsai and myget.org/bonsai-community are now at 97% storage capacity. There is also no option to create free MyGet accounts anymore (which means new contributors cannot push packages easily), and the upgrade path offers no guarantee of supporting the new NuGet protocol features we require (package deprecation, embedded licenses and icons, package type filtering).

Therefore we have been preparing for over a year the transition which is now almost fully finished. All but a few official packages have been transferred to nuget.org/bonsai, the package prefix has been reserved, and the full mirroring is expected to complete by the time 2.9 is out.

Call to Action

This announcement is a last call to action for maintainers of community packages which have not yet migrated their releases to nuget.org. We will not republish these packages to NuGet ourselves, unless we hear from you and agree on a plan of action. If you are affected by this and are facing difficulties of any kind, please reach out to us on this thread or on our other Community channels.