github/meteor
1
1
Fork 0
mirror of https://github.com/meteor/meteor.git synced 2026-05-02 03:01:46 -04:00
Code Issues Packages Projects Releases Wiki Activity

Mention release-based core package version constraints in History.md.

Browse Source
This commit is contained in:
Ben Newman
2017-02-07 17:55:31 -05:00
parent 33e4a6e658
commit ff4b00c774
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
History.md
View File

@@ -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)