From ff4b00c774ef4cbef9ddefea514b426d6694cf90 Mon Sep 17 00:00:00 2001 From: Ben Newman Date: Tue, 7 Feb 2017 17:55:31 -0500 Subject: [PATCH] Mention release-based core package version constraints in History.md. --- History.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/History.md b/History.md index 998df42b36..60ea6558a7 100644 --- a/History.md +++ b/History.md @@ -1,5 +1,18 @@ ## v.NEXT +* Versions of Meteor [core + packages](https://github.com/meteor/meteor/tree/release-1.4.3/packages) + are once again constrained by the current Meteor release. Before Meteor + 1.4, the current release dictated the exact version of every installed + core package, which meant newer core packages could not be installed + without publishing a new Meteor release. In order to support incremental + development of core packages, Meteor 1.4 removed all release-based + constraints on core package versions (#7084). Now, in Meteor 1.4.3, each + core package version must be patch-compatible with whatever version of + the package was current when the Meteor release was published. This + middle ground restores meaning to Meteor releases, yet still permits + patch updates to core packages. + * The `facebook` package has been split into: - `facebook-oauth` (the part that allows oauth w/ FB directly) and - `facebook-config-ui` (the Blaze configuration templates for accounts-ui)