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

Merge pull request #13349 from meteor/leonardo/update-docs

Browse Source 
Update Versions
This commit is contained in:
Denilson
2024-09-12 13:13:56 -04:00
committed by GitHub
parent b4b8865730 4a506f8132
commit cdcb4d1314
3 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
v3-docs/v3-migration-docs/breaking-changes/upgrading-packages.md
View File

@@ -20,7 +20,7 @@ Package.onUse((api) => {
});
```
Then you can publish your package and test it with Meteor 3.0, by running `meteor publish --release=3.0.1`.
Then you can publish your package and test it with Meteor 3.0, by running `meteor publish --release=3.0.3`.
## Changes for packages that do not use Meteor packages that had breaking change

8
v3-docs/v3-migration-docs/guide/publishing-packages.md
View File

@@ -1,11 +1,11 @@
## Publishing Packages
Publishing a Meteor package involves a few key steps, including setting up your package, testing it, and finally publishing it to the Meteor package repository. Here's a brief guide on how to publish Meteor packages using Meteor 3, specifically with the `meteor publish --release=3.0.1` command.
Publishing a Meteor package involves a few key steps, including setting up your package, testing it, and finally publishing it to the Meteor package repository. Here's a brief guide on how to publish Meteor packages using Meteor 3, specifically with the `meteor publish --release=3.0.3` command.
### Prerequisites
- Ensure you have Meteor 3 installed. You can check your Meteor version and automatically download it if it's missing:
```bash
meteor --version --release=3.0.1
meteor --version --release=3.0.3
```
- Have a Meteor developer account. You can create one at [Meteor's official website](https://www.meteor.com/).
@@ -87,10 +87,10 @@ meteor test-packages ./ --driver-package meteortesting:mocha
Once your package is ready and tested, you can publish it using the following command:
```bash
meteor publish --release=3.0.1
meteor publish --release=3.0.3
```
You can replace `3.0.1` with the appropriate release version. If you omit the `--release` flag, it will default to the latest official Meteor version, which at the time of this writing is Meteor 2. That way packages published without specifying a release will not be compatible with Meteor 3, as there will probably be a `fibers` related error.
You can replace `3.0.3` with the appropriate release version. If you omit the `--release` flag, it will default to the latest official Meteor version, which at the time of this writing is Meteor 2. That way packages published without specifying a release will not be compatible with Meteor 3, as there will probably be a `fibers` related error.
- **Login if prompted:**
You will be asked to log in with your Meteor developer account credentials if you aren't already logged in.

4
v3-docs/v3-migration-docs/index.md
View File

@@ -20,7 +20,7 @@ Meteor 3.0 is currently in its official version!
You can create a new Meteor 3.0 project by running the command below:
```bash
meteor create my-new-project --release 3.0.1
meteor create my-new-project --release 3.0.3
```
## How to upgrade from Meteor 2.x?
@@ -28,7 +28,7 @@ meteor create my-new-project --release 3.0.1
You can upgrade your Meteor 2.x project by running the command below inside your project folder:
```bash
meteor update --release 3.0.1
meteor update --release 3.0.3
meteor reset # resets project to a fresh state
```