Release 1.4.2.2 (and 1.4.2.3)

[benjamn]

Minor follow-up release to Meteor 1.4.2.1.

In addition to what's currently on devel, here are the issues I'm hoping to address with this release:

Detection of newly added files:

• https://forums.meteor.com/t/meteor-not-detecting-new-files/31151
• meteor-vue/vue-meteor#80
• #7975 (comment)
• #8008
• #7978 (comment)

Reify-related issues (possibly to be postponed to 1.4.3):

• #8021
• #7662
• #8030

[pozylon]

Very happy to see you guys adding new features to the accounts system and minimongo.

[laosb]

@benjamn Is it OK to add a compatibility breaking change (accounts-facebook splitting)in a patch version?

[benjamn]

@laosb You might be right… how much do those changes break backwards compatibility? We could always release those packages separately, later.

[laosb]

Basically if users update, they need to add one more package to get config UI.

[benjamn]

@laosb After thinking about it over the weekend, I've decided to remove the accounts-facebook reorganization changes from this release, so that the 1.4.2.2 will be smoother. We should still release new versions of those packages immediately after releasing 1.4.2.2.

[benjamn]

Please run meteor update --release 1.4.2.2-rc.1 and test any functionality that's important to you. I'd like to do the final release today or tomorrow. Also please let me know about any changes that I missed that can't wait for the next release.

[abernix]

I likely won't have a chance to test this tonight (your today).

I'm not aware of any other issues which cannot wait for the next release. The only other 'trending' issue that I've seen in the last couple weeks is that Uglify's lack of harmony features (on the published branch) seems to be rearing its head more and more (#8020, #7994, #5517). I also haven't had an opportunity to verify that those would be fixed with the harmony branch though so maybe that would be a better fit for 1.4.3 (reify, babel, etc.).

[benjamn]

Yeah, last I checked the harmony branch of UglifyJS was not ready for production, and was not a smooth upgrade. Crazy that they've survived this long without catching up to the times.

[abernix]

@benjamn I'd suggest merging #8045 as well. It implements code-style improvements to the new "skel" introduced with #7807 (which is surfacing for the first time in 1.4.2.2 thanks to 0466fdd above). It'd be nice to just use the "improved" version.

[benjamn]

After taking a closer look at #8045, even though Meteor 1.4.2.2 is already final (but not yet "recommended"), I think it's worth immediately publishing a 1.4.2.3 release with @dburles' changes. Lots of folks are going to encounter those skeleton files before they know anything else about Meteor, so it seems really important for them to demonstrate good style and code structure.

[abernix]

Good call on the move for 1.4.2.3. Also, if it's any assurance, I saw no issues with Meteor 1.4.2.2-rc.1 in my tests on my own apps.

[QHose]

Hi Ben,

I used your suggested beta for the file not change issue. It works better. But I noticed meteor does not recognize small changes consistently. E.g. When I make a A HREF with too much quotes. I save, then meteor shows the error. I remove the extra quote but it does not update.

<a href="{{URL_Youtube_concept_behind}}"" target="_blank">explained in this video</a>

to

<a href="{{URL_Youtube_concept_behind}}" target="_blank">explained in this video</a>

I saw the same thing yesterday when I had too much blaze }}}.

{{template}}}

to

{{template}}

[QHose]

mmm, could it be I press save too soon... and meteor is not yet checking my files?

[abernix]

👍 Can this also be added to the https://install.meteor.com/ script? (two separate places)