-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
[1.3beta12] Cannot downgrade #6366
Comments
Check your code out from source control. You shouldn't really be downgrading this way. That's what git is for. |
Thank you @hongbo-miao. So the update is global? I hoped that the meteor update is local, i.e. I can have different repos with different versions. |
@Obiwarn yeah, it is global. |
@Obiwarn can you paste in the rest of the error output? All of the visible version constraints look ok for the downgrade… |
I found this was an issue on other production apps too. Tested it with a skeleton app also. Removing
|
I believe this is caused by When you try to downgrade the packages remain but these demand beta versions. CURRENT SOLUTION Then remove You may also need to delete your Do a If needed, a Would love an official fix in the meteor tool though for the 1.3 release. |
I don't think we have every done this before in the case of changing packages. IMO the preferred way to downgrade should be to use version control or just back up the application before upgrading. If we really want to publish them for old Meteor we can, but personally I wouldn't be excited about establishing the precedent that we expect downgrading to work, because that severely limits the transformations we can do inside the upgrade. |
Could upgraders as in `.finished-upgraders` not be used in reverse when downgrading? It is more a use case for beta testing as I don't believe many downgrade stable versions. And the problem is only caused by upgraders such as the minifiers split.
|
If we wrote reliable reversible versions of every single one, then yes. |
@stubailo If it is one global Meteor version as @hongbo-miao said. What about enabling "per Project" Meteor versions? |
That's already the case. If you upgrade one app to Meteor 1.3 all of your other apps are unaffected and still run Meteor 1.2. |
Closing this in favor of #6431 |
After a brave
meteor update --release 1.3-beta.11
I wanted to downgrade with
meteor update --release 1.2.1
but got lots of errors:
... and so on.
The text was updated successfully, but these errors were encountered: