Updating to an incompatable version.

[zaphodddd]

Did it never occur to the update software team to check to see if a machine will be able to run the update??!!?
The app sure checks to see if it will run on the machine. And it wont. I'm in the middle of work, and the app politely asks for an update, no information about the update, and which promptly says it wont run on the machine. Its a breaking update, and no information about that.

Its a stupid simple check. And is the responsibility of the developer.

Not every machine is the same as the developers machine. We've had 'updates' for 50 years. We've been checking for requirements updates for 50 years. We have had changelogs for 50 years, and we have the ability to present any breaking changes to the user BEFORE they install the software. This is either lazy, ignorant, or arrogant. I can't decide which.

"Why are you using that version?"

• Red herring. Doesn't matter. The update broke a thing that was working. It's stupid simple to check that it will break a thing, and it should do it, so that it doesn't break a thing that is working. The idea that "this is not a concern" or "a user problem" if prevalent, and is built on a logical flaw.

Whats insidious that is that it happened from inside the very app that was working. It allows a user to click a button INSIDE the app, that destroys the app. Bad design.

[welcome]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.

You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

[mbektas]

@zaphodddd sorry about the bad experience caused by the auto-update. we will revisit our auto update process.

I added a section to the troubleshooting document for instructions to revert to an older version. It should help you revert to a previous compatible version for a resolution to your issue.

[JasonWeill]

@zaphodddd I'm sorry to hear about your bad experience with JupyterLab Desktop. The macOS version auto-updates without checking Electron's compatibility with your OS version and without displaying the release notes, which state that macOS 10.15 or later is required for JupyterLab Desktop 4.0.7-1.

All contributors to Jupyter projects are expected to follow the Jupyter Code of Conduct, which includes being considerate and respectful. Referring to the application's developers as "lazy, ignorant, or arrogant" for not checking whether an updated version is compatible with macOS 10.14 is not being considerate or respectful. As an open source project, we would gladly consider a pull request to add an OS compatibility check to the upgrade check. Please let us know if you need any assistance with your patch.