-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Release 1.4.1 #7580
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
Release 1.4.1 #7580
Conversation
|
Btw, Node CTC Meeting notes last week they just needed more folks to test the 4.5.0-rc as it had some important changes and hadn't got many folks on the RC yet. During yesterday's meeting, IBM said they have been using it internally without problems. It's still on the agenda for next week right now. I don't know how willing Meteor is to test the |
|
@abernix I don't see why not! |
|
Hmm, sadly, |
This reverts commit 64a9312. Although Meteor runs fine on Node 4.5.0, node-gyp doesn't know how to download libraries appropriate for RC releases, so it looks like we need to hold off on this upgrade until it's officially out.
This gives us a reliable place for node-gyp to find the necessary headers and libraries for compiling binary packages, instead of relying on the accessibility of $HOME and/or $USERPROFILE.
The node-gyp tool uses `process.env.HOME || process.env.USERPROFILE` to determine where it should install the .node-gyp directory containing Node headers and libraries, and we now preinstall that directory at dev_bundle/.node-gyp/, so (with this change) no download should be necessary.
These packages need to be installed when we run `npm install` in `bundle/programs/server` (which this commit ensures), but they don't need to be part of the dev bundle.
This package is depended upon by `cordova-lib`, and npm@3 hoists it to the top-level dev_bundle/lib/node_modules directory. We don't use this example app in Meteor, so we don't need it in the dev bundle. If it is ever needed, developers can run meteor npm install -g cordova-app-hello-world To include it in the dev bundle. It would be really great if we could remove cordova-lib's extra copy of npm, but that will probably have to wait until they update to npm@3.
Since we do not write .meteor-last-rebuild-version.json files when developers run `meteor npm install ...`, this commit saves us from unnecessarily rebuilding any freshly-installed binary npm dependencies when Meteor starts.
See #7495. Still some decisions to be made: - Should we make --all-packages the default? - How should we deal with *new* indirect dependencies? - Should we do anything about underpinning indirect dependencies when updating?
* Add --no-release-check option to skip release check * Add METEOR_NO_RELEASE_CHECK environment variable
It's time to begin the beta testing process for Meteor 1.4.1!
If you'd like to participate, as usual, keep an eye on the releases page for new entries with names like
release/[email protected], and update to the latest release by runningmeteor update --release 1.4.1-beta.nin a test application.Note that this release will not ship until Node 4.5.0 is released, but that seems imminent.