-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow opting into pre-releases per-package #46
Comments
Installing a pre-release version in the package manager automatically opt-in the user for subsequent pre-release updates of the package. The opt-in is active up to the next stable version. |
And that's the crux of this FR: to be able to opt in to the latest version of a package in perpetuity, even if it's a prerelease, as part of the automatic upgrade process. |
Done, here's a test build (backup registry.db first): https://ci.appveyor.com/api/buildjobs/i4xdsqsx88bph2i3/artifacts/build%2Freaper_reapack-x64.dll. |
Wow, that was fast! @cfillion I tested out all the scenarios I could think of related to moving between releases and prereleases, and everything looks good. to me. 👍 Thanks! |
Currently the feature to automatically install prereleases is a global setting. This should also be available on a package-by-package basis, overriding the global setting.
Because of this, Reaticulate distributes both a release ReaPack and a prerelease ReaPack, so that users on the prerelease track automatically receive updates. But if ReaPack provided the ability to enable prereleases for specific packages only, rather than globally, I could consolidate these ReaPacks.
The text was updated successfully, but these errors were encountered: