Skip to content
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

Error updating Meteor from 1.4.4.2 to 1.4.4.3 #8759

Closed
MartiniHenry1988 opened this issue Jun 5, 2017 · 5 comments
Closed

Error updating Meteor from 1.4.4.2 to 1.4.4.3 #8759

MartiniHenry1988 opened this issue Jun 5, 2017 · 5 comments

Comments

@MartiniHenry1988
Copy link

I am facing errors after updating meteor by running :

meteor update --patch

=> Meteor 1.5 is available. Update this project with 'meteor update'.
=> Started MongoDB.                           
=> Errors prevented startup:                  
   
   While selecting package versions:
   error: Potentially incompatible change required to top-level dependency:
   meteor-base 1.0.4, was 1.1.0.
   Constraints on package "meteor-base":
   * meteor-base@1.0.4 <- top level
   * meteor-base@1.0.4 <- top level
   
   To allow potentially incompatible changes to top-level dependencies, you
   must pass --allow-incompatible-update on the command line.
   
=> Your application has errors. Waiting for file change.

Is there any workaround to fix this?

@matteosaporiti
Copy link

matteosaporiti commented Jun 6, 2017

I also had this.
I solved by manually modifying the meteor-base version in .meteor/versions (was @1.1.0, I put @1.0.4).

dynamic-import was also added to my packages (which is quite strange since it's a 1.5 feature).

@duffar
Copy link

duffar commented Jun 6, 2017

I'm encountering the same issue with incompatible changes to meteor-base and dynamic-import. I too was surprised to see dynamic-imports added to my 1.4.4.x project.

Kind of disheartening to see this kind of failure in core meteor packages on a patch upgrade. I ran into something similar in the 1.4.2.x patch upgrade. I'm not sure why this isn't showing up in their upgrade testing.

Thanks for the resolution tip. I'll probably give 1.5 a shot or go back to 1.4.4.2 as I don't like being on a hybrid release.

@iamnives
Copy link

iamnives commented Jun 7, 2017

Had the same problem didnt touch anything updated to 1.5 with meteor update.
Everything works!

@duffar
Copy link

duffar commented Jun 7, 2017

Same results here. Moving to 1.5 worked. Which I'm happy about.
But updating to the patch should have worked too. Clearly a gap in the upgrade testing path.
Thanks @amneves

@MartiniHenry1988
Copy link
Author

Updating to Meteor 1.5 fixed it for me. So if someone else is facing this issue, just run meteor update command again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants