From 73fcfeeccf0320b30bf5d135b79f1f0d369124de Mon Sep 17 00:00:00 2001
From: Gabriel Grubba <70247653+Grubba27@users.noreply.github.com>
Date: Fri, 29 Dec 2023 15:57:07 -0300
Subject: [PATCH 1/5] Update to use beta.0
---
guide/source/3.0-migration.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/guide/source/3.0-migration.md b/guide/source/3.0-migration.md
index eef027119c..7591356327 100644
--- a/guide/source/3.0-migration.md
+++ b/guide/source/3.0-migration.md
@@ -7,7 +7,7 @@ description: How to migrate your application to Meteor 3.0.
## What's the status of version 3.0?
-**Latest version:** `3.0-alpha.20`
+**Latest version:** `3.0-beta.0`
**Node.js version:** `20.9.0 LTS`
Meteor 3.0 is in alpha and not recommended for production. You can check the "[Release 3.0 Pull Request](https://github.com/meteor/meteor/pull/12359)" to see what is being changed.
@@ -112,7 +112,7 @@ findOne is not available on the server. Please use findOneAsync instead.
You can create a new Meteor 3.0 project by running the command below:
```bash
-meteor create my-new-project --release 3.0-alpha.20
+meteor create my-new-project --release 3.0-beta.0
```
### How to update from version 2?
@@ -120,7 +120,7 @@ meteor create my-new-project --release 3.0-alpha.20
You can update your Meteor 2.x project by running the command below inside your project folder:
```bash
-meteor update --release 3.0-alpha.20
+meteor update --release 3.0-beta.0
```
### How to follow the progress on version 3?
@@ -143,7 +143,7 @@ The migration will look like this:
```js
// in you package.js
Package.onUse((api) => {
- api.versionsFrom(['1.10', '2.3', '3.0-alpha.20']);
+ api.versionsFrom(['1.10', '2.3', '3.0-beta.0']);
// ^^^^^^^ for testing your package with meteor 3.0
api.versionsFrom(['1.10', '2.3', '3.0']);
From 388e235c3add91afc2d47626a3deeaaf679220e2 Mon Sep 17 00:00:00 2001
From: emmanuel <154705254+codesmith-emmy@users.noreply.github.com>
Date: Tue, 2 Jan 2024 17:52:57 +0100
Subject: [PATCH 2/5] Update README.md
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Part of README was respectfully rephrased to help developers who may have limited English proficiency. ๐๐ฝ
---
README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
index 8cc560ad5c..ab784cd404 100644
--- a/README.md
+++ b/README.md
@@ -46,7 +46,7 @@ Use the same code whether youโre developing for web, iOS, Android, or desktop
# ๐ฅ Getting Started
-How about trying a getting started tutorial in your favorite technology?
+How about trying a tutorial to get started with your favorite technology?
| [
React](https://react-tutorial.meteor.com/) |
| - |
From e158584b9f679cad4a3dd685012bf0894d06c962 Mon Sep 17 00:00:00 2001
From: harryadel
Date: Sat, 13 Jan 2024 12:48:31 +0200
Subject: [PATCH 3/5] Add note about mtest
---
guide/source/writing-atmosphere-packages.md | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/guide/source/writing-atmosphere-packages.md b/guide/source/writing-atmosphere-packages.md
index 0449d0690d..bbe4699ad6 100644
--- a/guide/source/writing-atmosphere-packages.md
+++ b/guide/source/writing-atmosphere-packages.md
@@ -296,6 +296,12 @@ Package.onTest(function(api) {
From within your test entry point, you can import other files as you would in the package proper.
+You can also use [`mtest`](https://github.com/zodern/mtest) to test your packages like so:
+
+`mtest --package ./ --once 2.14`
+
+Which helps immensely if you'd like to test your package in CI/CD setup. You can see an example [here](https://github.com/monti-apm/monti-apm-agent/blob/master/.github/workflows/test.yml).
+
You can read more about testing in Meteor in the [Testing article](testing.html).
Publishing your package
From 411b5efa9cb327d60a49c17f0e16275ea3e97092 Mon Sep 17 00:00:00 2001
From: harryadel
Date: Sat, 13 Jan 2024 12:50:35 +0200
Subject: [PATCH 4/5] format script using bash
---
guide/source/writing-atmosphere-packages.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/guide/source/writing-atmosphere-packages.md b/guide/source/writing-atmosphere-packages.md
index bbe4699ad6..31a3fa8738 100644
--- a/guide/source/writing-atmosphere-packages.md
+++ b/guide/source/writing-atmosphere-packages.md
@@ -298,7 +298,9 @@ From within your test entry point, you can import other files as you would in th
You can also use [`mtest`](https://github.com/zodern/mtest) to test your packages like so:
-`mtest --package ./ --once 2.14`
+```bash
+mtest --package ./ --once 2.14
+```
Which helps immensely if you'd like to test your package in CI/CD setup. You can see an example [here](https://github.com/monti-apm/monti-apm-agent/blob/master/.github/workflows/test.yml).
From 44e3890d6f5d2bea942006c225deba663192bec5 Mon Sep 17 00:00:00 2001
From: Harry Adel
Date: Sat, 20 Jan 2024 15:20:10 +0200
Subject: [PATCH 5/5] My greatest contribution ever
Meteor would crumble without me
---
README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
index ab784cd404..f608b00f3d 100644
--- a/README.md
+++ b/README.md
@@ -10,7 +10,7 @@
[](https://app.travis-ci.com/github/meteor/meteor)
[](https://app.circleci.com/pipelines/github/meteor/meteor?branch=devel)
-[](https://meteor.com)
+[](https://meteor.com)