Totally broken #25723
Comments
Speaking as someone somewhat familiar with this repo/code: Some incompatibility with a few The package upload/download issue is because the website atom.io has been flaky, and that website/server hosts the package registry and API for Atom packages. If it were me, I would be more conservative and base the final release on Electron 9, since Electron 11 only made it to Atom Beta and didn't get super wide testing, had the few known issues such as with the I can see how easy it would be to just publish from master and not flag the Electron 11 bump as a problem for some users. This repo and its tooling are hard to work with. It's a huge code-base to be familiar with if you're not actively knee-deep in it on the daily. (And it'd be a bit awkward to leave out some large amount of effort and PRs which various people have contributed to If you get the point of the sunset message (I think we all do), I guess a workaround could be to disable automatic updates and use the old 1.60.x stable version. Particularly if you need those ide packages. |
I recommend switching to Photon, it's a community fork of Atom which fixes a lot of things and keeps Atom going |
I'm assuming you are talking about Pulsar? |
Yes lmao :P |
How frustrating for the last "sunsetting" update to the program to actually break all of the functionality.
Since 1.63 update on macOS (even with 1.63.1)
This is in addition to the package downloading/uploading which has already been broken for several months.
I know no one will look at this or care, but the way in which this project was sabotaged and killed by Microsoft is really shameful.
The text was updated successfully, but these errors were encountered: