Release 1.3.4.3 #7369
Release 1.3.4.3 #7369
Conversation
@benjamn is there a chance of releasing another If a release not require any complex merging, of course. |
@kachkaev of course! I haven't even rebased https://github.com/meteor/meteor/tree/release-1.4 against these changes yet :) |
The 0.6.17 version was already taken by another branch, though I'm not sure which one.
With the simultaneous development of Meteor 1.4, npm-bcrypt@0.8.7 has already been published, but we very much do not want to use that version with Meteor 1.3.4.3, since it doesn't work with Node 0.10.46.
This comment has been minimized.
This comment has been minimized.
This commit message was accidentally |
This comment has been minimized.
This comment has been minimized.
@benjamn when I upgraded |
This comment has been minimized.
This comment has been minimized.
Yes, the downgrade was deliberate, since |
This comment has been minimized.
This comment has been minimized.
@benjamn sorry I wasn't clear. I meant the passwords themselves, not |
This comment has been minimized.
This comment has been minimized.
@benjamn just ignore this completely, apologies. I just tested this setting a password with |
This comment has been minimized.
This comment has been minimized.
+1. I was wondering if dev_bundle should really be ignored. Thanks for this. |
This comment has been minimized.
This comment has been minimized.
mquandalle
commented on tools/static-assets/skel/.meteor/.gitignore
in 9e6ebde
Jul 19, 2016
@benjamn Shouldn’t this be removed now? |
This comment has been minimized.
This comment has been minimized.
My plan is to revert this whole commit in Meteor 1.4, though I don't see any harm in continuing to ignore |
Unfortunately, the following claim in the release notes for the 1.3.4.2 release was not entirely true:
meteor node
andmeteor npm
commands now respect.meteor/release
when resolving which versions ofnode
andnpm
to invoke. Note that you mustmeteor update
to 1.3.4.2 before this logic will take effect, but it will work in all app directories after updating, even those pinned to older versions. #7338Specifically, running
meteor update
to update to 1.3.4.2 was not actually enough to modify the~/.meteor/meteor
symlink (orAppData\Local\.meteor\meteor.bat
on Windows), which prevented the new behavior ofmeteor node
andmeteor npm
from taking effect.Thanks to @rhettlivingston for providing quick feedback on these concerns!