[solved] Packages not updated even with patch version update

packages
1

I tried to update My Meteor app from 2.1 to 2.2.1 inlcuding --all-packages and I found a great bunch of incompatible packages:

The following top-level dependencies were not updated to the very latest version available:
 * accounts-base 1.9.0 (2.0.0 is available)   
 * accounts-password 1.7.1 (2.0.0 is available)
 * ecmascript 0.15.1 (0.15.2 is available)    
 * email 2.0.0 (2.1.0 is available)           
 * meteor-base 1.4.0 (1.5.1 is available)     
 * mongo 1.11.1 (1.12.0 is available)         
                                              
Newer versions of the following indirect dependencies are available:
 * ddp-client 2.4.1 (2.5.0 is available)      
 * ddp-rate-limiter 1.0.9 (1.1.0 is available)
 * ddp-server 2.3.3 (2.4.0 is available)      
 * dynamic-import 0.6.0 (0.7.1 is available)  
 * http 1.4.4 (2.0.0 is available)            
 * launch-screen 1.2.1 (1.3.0 is available)   
 * minimongo 1.6.2 (1.7.0 is available)       
 * promise 0.11.2 (0.12.0 is available)       
 * service-configuration 1.0.11 (1.1.0 is available)
 * socket-stream-client 0.3.3 (0.4.0 is available)
 * typescript 4.2.2 (4.3.2 is available)      
 * webapp 1.10.1 (1.11.1 is available)

I can understand this for those packages with major version steps but why aren’t minor or even patch version updates applied?

ecmascript 0.15.1 (0.15.2 is available)

Can packages declare actually fixed dependencies?

2

The only reason these would not get updated is if they are fixed to a particular Meteor release. It is unlikely with patch releases, but it can happen. These get fixed due since when releasing a Meteor version all the packages that relay on it automatically have api.versionsFrom('2.3') // or the particular release included in them.

3

Thank you, I still can’t find the source of this, I even can’t start the app and the “top-level” versions of the packages don’t match the versions in .meteor/versions:

=> Errors prevented startup:                  
   
   While selecting package versions:
   error: Conflict: Constraint blaze@2.4.0 is not satisfied by blaze 2.3.4.
   Constraints on package "blaze":
   * blaze@=2.3.4 <- top level
   * blaze@2.4.0 <- launch-screen 1.2.1 <- mobile-experience 1.1.0
   * blaze@2.3.2 <- blaze-html-templates 1.1.2
   * blaze@2.3.2 <- ui 1.0.13 <- blaze-html-templates 1.1.2
   * blaze@2.3.2 <- spacebars 1.0.15 <- blaze-html-templates 1.1.2
   * blaze@2.3.2 <- templating-runtime 1.3.2 <- blaze-hot 1.1.0
   * blaze@2.3.4 <- accounts-base 1.9.0
   * blaze@2.5.0 <- alanning:roles 3.3.0
   * blaze@2.5.0 <- blaze-hot 1.1.0
   
   Conflict: Constraint templating@1.4.0 is not satisfied by templating 1.3.2.
   Constraints on package "templating":
   * templating@=1.3.2 <- top level
   * templating@1.4.0 <- launch-screen 1.2.1 <- mobile-experience 1.1.0
   * templating@1.3.2 <- blaze-html-templates 1.1.2
   
   Conflict: Constraint blaze@2.5.0 is not satisfied by blaze 2.3.4.
   Constraints on package "blaze":
   * blaze@=2.3.4 <- top level
   * blaze@2.4.0 <- launch-screen 1.2.1 <- mobile-experience 1.1.0
   * blaze@2.3.2 <- blaze-html-templates 1.1.2
   * blaze@2.3.2 <- ui 1.0.13 <- blaze-html-templates 1.1.2
   * blaze@2.3.2 <- spacebars 1.0.15 <- blaze-html-templates 1.1.2
   * blaze@2.3.2 <- templating-runtime 1.3.2 <- blaze-hot 1.1.0
   * blaze@2.3.4 <- accounts-base 1.9.0
   * blaze@2.5.0 <- alanning:roles 3.3.0
   * blaze@2.5.0 <- blaze-hot 1.1.0
   
   Conflict: Constraint templating-runtime@1.4.0 is not satisfied by templating-runtime 1.3.2.
   Constraints on package "templating-runtime":
   * templating-runtime@=1.3.2 <- top level
   * templating-runtime@1.3.2 <- templating 1.3.2 <- blaze-html-templates 1.1.2
   * templating-runtime@1.4.0 <- blaze-hot 1.1.0

However, the versions for these packages are in .meteor/versions (among others):

accounts-base@1.9.0
# ...
blaze@2.5.0
blaze-hot@1.1.0
blaze-html-templates@1.2.1
blaze-tools@1.1.2
# ...
launch-screen@1.2.1
# ...
mobile-experience@1.1.0
# ...
templating@1.4.1
templating-compiler@1.4.1
templating-runtime@1.5.0
templating-tools@1.2.0
# ...
ui@1.0.13

I totally don’t get it. I never had any issues with package updates before and what I see makes no sense to me.

Edit: updating Meteor to 2.3.1 did not fix this unfortunately :frowning:

4

If updating to the latest version of Meteor does not fixes the issue then there probably is some package that is causing havoc or some other constrain. In what you have provided it looks like something in top level. Try to force them a few times.

5

You were right, I commented all packages but those included in a new Blaze project and it seems one of the packages went rogue :sweat_smile: