Confusion between meteor update and meteor update --all-packages

ffxsam · January 19, 2017, 5:58am

I figured using --all-packages would update everything, but it doesn’t seem that it does.

Results of meteor update --all-packages:

This project is already at Meteor 1.4.2.3, the latest release.
Your top-level dependencies are at their latest compatible versions.

The following top-level dependencies were not updated to the very latest
version available:
 * jagi:astronomy 2.3.9 (2.3.12 is available)
 * static-html 1.1.13 (1.2.0 is available)

Newer versions of the following indirect dependencies are available:
 * blaze 2.2.0 (2.3.0 is available)
 * caching-html-compiler 1.0.7 (1.1.0 is available)
 * coffeescript 1.11.1_4 (1.12.0_1 is available)
 * modules-runtime 0.7.7 (0.7.8 is available)
 * npm-mongo 2.2.11_2 (2.2.16_1 is available)
 * spacebars-compiler 1.0.13 (1.1.0 is available)
 * templating 1.2.15 (1.3.0 is available)
 * templating-compiler 1.2.15 (1.3.0 is available)
 * templating-runtime 1.2.15 (1.3.0 is available)
 * templating-tools 1.0.5 (1.1.0 is available)
To update one or more of these packages, pass their names to
`meteor update`, or just run `meteor update --all-packages`.

Results of meteor update:

This project is already at Meteor 1.4.2.3, the latest release.

Changes to your projects package version selections from updating package
versions:

blaze                  upgraded from 2.2.0 to 2.2.1
caching-html-compiler  upgraded from 1.0.7 to 1.1.0
jagi:astronomy         upgraded from 2.3.9 to 2.3.12
modules-runtime        upgraded from 0.7.7 to 0.7.8
npm-mongo              upgraded from 2.2.11_2 to 2.2.16_1
spacebars-compiler     upgraded from 1.0.13 to 1.1.0
static-html            upgraded from 1.1.13 to 1.2.0
templating-tools       upgraded from 1.0.5 to 1.1.0


Newer versions of the following indirect dependencies are available:
 * blaze 2.2.1 (2.3.0 is available)
 * coffeescript 1.11.1_4 (1.12.0_1 is available)
 * templating 1.2.15 (1.3.0 is available)
 * templating-compiler 1.2.15 (1.3.0 is available)
 * templating-runtime 1.2.15 (1.3.0 is available)
To update one or more of these packages, pass their names to
`meteor update`, or just run `meteor update --all-packages`.

The --all-packages option is not documented in meteor help update, so it’s not clear what this is actually doing.

robfallows · January 19, 2017, 11:32am

History.md v1.4.1 states:

The meteor update command now supports an --all-packages flag to update all packages (including indirect dependencies) to their latest compatible versions, similar to passing the names of all your packages to the meteor update command. (Emphasis mine).

So I assume, that those packages which weren’t upgraded are not compatible for some reason. Not a very satisfactory answer, I know.

ffxsam · January 19, 2017, 6:52pm

It seems the correct course to update everything is to first run meteor update followed by meteor update --all-packages.

crenshininbon · February 8, 2017, 8:15am

Coffeescript isn’t updated to 1.12.0_1 even with:

meteor update all-packages

This project is already at Meteor 1.4.2.5, the latest release.
Your top-level dependencies are at their latest compatible versions.

The following top-level dependencies were not updated to the very latest
version available:
 * coffeescript 1.11.1_4 (1.12.0_1 is available)

Any hint is appreciated.

crenshininbon · February 8, 2017, 8:25am

Uninstalling and installing with specific version number fixed it:

meteor remove coffeescript
                                              
Changes to your project's package version selections:
                                              
coffeescript  removed from your project       

coffeescript: removed dependency

Then:

meteor add coffeescript@1.12.0_1
                                                                                
Changes to your project's package version selections:
                                              
babel-compiler+  upgraded from 6.13.0 to 6.15.0-beta.0
coffeescript     added, version 1.12.0_1
meteor+          upgraded from 1.6.0 to 1.6.1-rc.1

                                              
+ In order to resolve constraints, we had to use experimental versions of
these
packages.
                                              
coffeescript: Javascript dialect with fewer braces and semicolons

It looks as if meteor+ and babel-compiler+ keep the version down to 1.11. because it’s in beta/RC state … guess.

cstrat · June 28, 2021, 11:44pm

I am still having this challenge… using --all-packages doesn’t force the update.

I’ve tried removing/adding packages manually but can’t seem to break the dependency cycle on one of the old versions.

I’ve removed the version pin in the packages folder.

Any ideas?

wojtek · July 8, 2021, 5:34pm

Sadly I’m not writing in with an answer. I would also like to find a solution for this. Can we get Filipe on here?

wojtek · July 8, 2021, 6:25pm

@filipenevola As per your tweeter suggestion, here’s the output from my all package update. I have also tried updating random ones directly in the .meteor/versions and .meteor/packages files and they just get reverted to these versions. I suspect it’s an incompatibility problem somehow, but I’m not sure what the strategy to go about sorting this out is. Anyway, here’s the output;

Any help would be greatly appreciated.

I understand that these are the latest compatible versions but how can I figure out what is blocking me from moving to newer versions? Seems like I really should want to be on the latest versions of ddp packages. I guess one of the other ones is blocking that upgrade, but which one?

I just realised that the first screenshot is just update, but update all packages shows the same exact output;

rjdavid · July 8, 2021, 11:47pm

Those packages are for Meteor 2.3 which is not yet recommended. You can upgrade manually to 2.3 to get the new packages

@storyteller, any possibility for the output to include the minimum meteor version? Seems many devs are getting this issue everytime there is a new version that is not yet recommended

storyteller · July 8, 2021, 11:50pm

An interesting idea! I’ll look into it.

wojtek · July 9, 2021, 7:24am

That’s great. I’ll just wait for 2.3 to drop. What I didn’t want is to fall behind and end up with stale dependencies. I’ve been there before and it’s not fun at all

Thanks a million.

storyteller · July 9, 2021, 2:34pm

OK, so I’ve looked on the data that is being returned and sadly I can’t get write out the Meteor version that the package requires as it is tied to actual package version so instead I have added an explainer why packages might not update.