Release 2.7.2

docs/history.md

@@ -1,3 +1,28 @@
+## 2.7.2, 2022-04-XX
+
+#### Highlights
+
+#### Breaking Changes
+N/A
+#### Migration Steps
+
+#### Meteor Version Release
+
+* `mongo@1.15.0`
+  - New option `Meteor.settings.packages.mongo.reCreateIndexOnOptionMismatch` for case when an index with the same name, but different options exists it will be re-created. 
+  - If there is an error on index creation Meteor will output a better message naming the collection and index where the error occured. [PR](https://github.com/meteor/meteor/pull/11995).
+* `modern-browsers@0.1.8`
+  - New api `getMinimumBrowserVersions` to access the `minimumBrowserVersions`. [PR](https://github.com/meteor/meteor/pull/11998).
+* `socket-stream-client@0.5.0`
+  - Ability to disable sockjs on client side. [PR](https://github.com/meteor/meteor/pull/12007/).
+*`meteor-node-stubs@1.2.2`:
+  - Fix using meteor-node-stubs in IE. [PR](https://github.com/meteor/meteor/pull/12014).
+* New ARCH environment variable that permit users to set uname info. [PR](https://github.com/meteor/meteor/pull/12020).
+* Skeleton dependencies updated.
+* New Tailwind skeleton. [PR](https://github.com/meteor/meteor/pull/12000).
+
+#### Independent Releases
+
 ## v2.7.1, 2022-03-31
 
 #### Highlights
@@ -31,6 +56,7 @@
 ## v2.7, 2022-03-24
 
 #### Highlights
+* Bump node version to 14.19.1
 * TailwindCSS 3.x support
 * Typescript `4.5.4` upgrade
 * New core package: `accounts-2fa`

docs/source/api/accounts.md

@@ -227,9 +227,10 @@ First, add the service configuration package:
 meteor add service-configuration
 ```
 
-Then, in your app (this example is for the Weebo service):
+Then, inside the server of your app (this example is for the Weebo service), import `ServiceConfiguration`:
 
 ```js
+import { ServiceConfiguration } from 'meteor/service-configuration';
 ServiceConfiguration.configurations.upsert(
   { service: 'weibo' },
   {

docs/source/api/collections.md

@@ -408,6 +408,22 @@ Example defining a simple index on Players collection in Meteor:
 Players.createIndex({ userId: 1 }, { name: 'user reference on players' });
 ```
 
+Sometimes you or a package might change an already established indexes. This might throw an error and prevent a startup. 
+For cases where you can afford to re-build indexes or the change affect too many indexes you can set the `reCreateIndexOnOptionMismatch` 
+to true in your `settings.json`:
+
+```json
+{
+  "packages": {
+    "mongo": {
+      "reCreateIndexOnOptionMismatch": true
+    }
+  }
+}
+```
+
+> You should use this option only when you are dealing with a change across many indexes and it is not feasible to fix them manually and you can afford the re-building of the indexes as this will destroy the old index and create a new one. Use this carefully.
+
 {% apibox "Mongo.Collection#allow" %}
 
 {% pullquote warning %}

docs/source/environment-variables.md

@@ -28,6 +28,11 @@ Setting `DDP_DEFAULT_CONNECTION_URL` when building (`meteor build`)  will define
 
 In the event that your own deployment platform does not support WebSockets, or you are confident that you will not benefit from them, setting this variable with `DISABLE_WEBSOCKETS=1` will explicitly disable WebSockets and forcibly resort to the fallback polling-mechanism, instead of trying to detect this automatically.
 
+## DISABLE_SOCKJS
+(_development, production_)
+
+Set `DISABLE_SOCKJS=1` if you want to use the native WebSocket implementation instead of SockJS on the client side, for example, if you want to use a custom WebSocket implementation (e.g. [uWebSockets.js](https://github.com/uNetworking/uWebSockets.js/)) on the server side.
+
 ## HTTP_FORWARDED_COUNT
 (_production_)
 

docs/source/packages/fetch.md

@@ -40,20 +40,25 @@ import { Meteor } from 'meteor/meteor';
 import { fetch, Headers } from 'meteor/fetch';
 
 async function postData (url, data) {
-    const response = await fetch(url, {
-        method: 'POST', // *GET, POST, PUT, DELETE, etc.
-        mode: 'cors', // no-cors, *cors, same-origin
-        cache: 'no-cache', // *default, no-cache, reload, force-cache, only-if-cached
-        credentials: 'same-origin', // include, *same-origin, omit
-        headers: new Headers({
-            Authorization: 'Bearer my-secret-key',
-            'Content-Type': 'application/json'
-        }),
-        redirect: 'follow', // manual, *follow, error
-        referrerPolicy: 'no-referrer', // no-referrer, *no-referrer-when-downgrade, origin, origin-when-cross-origin, same-origin, strict-origin, strict-origin-when-cross-origin, unsafe-url
-        body: JSON.stringify(data) // body data type must match "Content-Type" header
-    });
-    return response.json();
+    try {
+      const response = await fetch(url, {
+          method: 'POST', // *GET, POST, PUT, DELETE, etc.
+          mode: 'cors', // no-cors, *cors, same-origin
+          cache: 'no-cache', // *default, no-cache, reload, force-cache, only-if-cached
+          credentials: 'same-origin', // include, *same-origin, omit
+          headers: new Headers({
+              Authorization: 'Bearer my-secret-key',
+              'Content-Type': 'application/json'
+          }),
+          redirect: 'follow', // manual, *follow, error
+          referrerPolicy: 'no-referrer', // no-referrer, *no-referrer-when-downgrade, origin, origin-when-cross-origin, same-origin, strict-origin, strict-origin-when-cross-origin, unsafe-url
+          body: JSON.stringify(data) // body data type must match "Content-Type" header
+      });
+      const data = await response.json();
+      return response(null, data);
+    } catch (err) {
+      return response(error, null);
+    }
 }
 
 const postDataCall = Meteor.wrapAsync(postData);

guide/source/deployment.md

@@ -129,7 +129,7 @@ Galaxy is a distributed system that runs on Amazon AWS. If you understand what i
 
 In order to deploy to Galaxy, you'll need to [sign up for an account](https://www.meteor.com/galaxy/signup), and separately provision a MongoDB database (see below).
 
-Once you've done that, it's easy to [deploy to Galaxy](http://galaxy-guide.meteor.com/deploy-guide.html). You need to [add some environment variables to your settings file](http://galaxy-guide.meteor.com/environment-variables.html) to point it at your MongoDB, and you can deploy with:
+Once you've done that, it's easy to [deploy to Galaxy](https://galaxy-guide.meteor.com/deploy-to-galaxy.html). You need to [add some environment variables to your settings file](http://galaxy-guide.meteor.com/environment-variables.html) to point it at your MongoDB, and you can deploy with:
 
 ```bash
 DEPLOY_HOSTNAME=galaxy.meteor.com meteor deploy your-app.com --settings production-settings.json

meteor

@@ -4,15 +4,20 @@ BUNDLE_VERSION=14.19.1.0
 
 # OS Check. Put here because here is where we download the precompiled
 # bundles that are arch specific.
-UNAME=$(uname)
+# Use of : "${ARCH:=$(uname)}" assignment permits users to set their
+# architecture manually; this is useful for multi-arch systems whose
+# uname executables may sometimes return different architectures in
+# different contexts.
+#   Ex: ARCH=arm64 meteor ARGS...;
+UNAME="$(uname)"
 if [ "$UNAME" != "Linux" -a "$UNAME" != "Darwin" ] ; then
     echo "Sorry, this OS is not supported."
     exit 1
 fi
 
 if [ "$UNAME" = "Darwin" ] ; then
     if [ "arm64" == "$(uname -m)" ]; then
-      ARCH="arm64"
+      : "${ARCH:=arm64}"
     else
       if [ "i386" != "$(uname -p)" -o "1" != "$(sysctl -n hw.cpu64bit_capable 2>/dev/null || echo 0)" ] ; then
 
@@ -21,10 +26,10 @@ if [ "$UNAME" = "Darwin" ] ; then
           echo "Only 64-bit and arm64 processors are supported at this time."
           exit 1
       fi
-      ARCH="x86_64"
+      : "${ARCH:=x86_64}"
     fi
 elif [ "$UNAME" = "Linux" ] ; then
-    ARCH="$(uname -m)"
+    : "${ARCH:=$(uname -m)}"
     if [ "$ARCH" != "x86_64" ] ; then
         echo "Unsupported architecture: $ARCH"
         echo "Meteor only supports x86_64"

npm-packages/meteor-installer/README.md

@@ -12,6 +12,9 @@ npm install -g meteor
 
 | NPM Package | Meteor Official Release |
 |-------------|-------------------------|
+| 2.7.3       | 2.7.2                   |
+| 2.7.2       | 2.7.1                   |
+| 2.7.1       | 2.7                     |
 | 2.7.0       | 2.7                     |
 | 2.6.2       | 2.6.1                   |
 | 2.6.1       | 2.6                     |

npm-packages/meteor-installer/config.js

@@ -1,7 +1,7 @@
 const path = require('path');
 const os = require('os');
 
-const METEOR_LATEST_VERSION = '2.7';
+const METEOR_LATEST_VERSION = '2.7.2';
 const sudoUser = process.env.SUDO_USER || '';
 function isRoot() {
   return process.getuid && process.getuid() === 0;

npm-packages/meteor-installer/package.json

@@ -1,6 +1,6 @@
 {
   "name": "meteor",
-  "version": "2.7.0",
+  "version": "2.7.3",
   "description": "Install Meteor",
   "main": "install.js",
   "scripts": {