Bonsai package feed outage and next steps

[glopesdev]

As several of you realized, the official Bonsai package and community feeds are down as of late night on Tuesday, 25th July. This is a frustrating and unfortunate consequence of an extended outage of MyGet.org package hosting services.

Communication has been very sparse despite the multiple projects and companies affected and there is currently no estimate of when the service will be restored. Thankfully the package index has been partially restored a few hours ago and we have now been able to recover a backup snapshot of all the packages, which means no information has been lost.

What next?

Although we don't know yet when (or if) this outage will be fully resolved, this event has accelerated our resolve to move away from MyGet for hosting the official Bonsai package feeds. We had been planning to do this anyway now that nuget.org has much improved filtering and searching functionality, but we have decided to move the roadmap forward. The migration will now take effect as of the upcoming Bonsai 2.8, which is in the final stages of preparation.

For those of you who will be installing Bonsai 2.8, no changes will need to be done. The new installer will automatically update the links to the new feeds and everything should work the same. The new portable installer will also be updated with the new feed links.

For existing deployments we have repackaged below a portable installer with a configuration NuGet.config file pointing to our backup feed. You can download it and update any existing config files with the new links. We will be updating this announcement has soon as we have stabilized the migration strategy. Our plan is to move existing feeds to feedz.io and long-term migrate the entire community feed to nuget.org, but we will provide more details soon.

SEE UPDATE BELOW

For community package maintainers

If you have uploaded packages to the Bonsai community feed, we highly recommend that you create an account and also upload them to nuget.org if you can. This way we can guarantee a public mirror for all community content that will likely not go away anytime soon. If you do not have access to backups of your community package artifacts, please contact us on Discord or discussions and we can arrange backup access.

We have currently no plans to upload community packages ourselves to nuget.org since this would compromise package author provenance (we would effectively become authors and owners of those packages). If you would still like us to do it anyway for your specific package, please get in touch and we can discuss different options.

[glopesdev]

The outage seems to be now fully resolved, so we have removed the link to the repackaged portable installer. The normal portable installer can be used safely for the time being.

We remain committed to our plans of migrating all our community feeds to nuget.org ASAP, so if you are a community package maintainer, please consider uploading your package to nuget.org in addition to our community feed. Do contact us if you have any questions.