-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Prevent people from loading incompatible packages via changing enviroments between loads #36372
Labels
packages
Package management and loading
Comments
Also xref #35663 |
I think when activating environments we should first check all loaded packages and if they are not compatible with the environment we should error. I think in 1.9 that is finally relatively easy as we record the versions of packages when we load them. |
Alternatively, something like #44329. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think many people have known this is possible for a while.
Because compatibility is checked at package install time on a per enviroment basis.
And because modules are not reloaded (ever), including after changing enviroments.
Today I think I saw this in the wild.
Here is a way to reproduce what i saw posted in Slack:
Revise will then flip-out because the API of CodeTracking is not what it said it was compatible with.
The text was updated successfully, but these errors were encountered: