2.6 KiB
title, description
| title | description |
|---|---|
| Migrating to Meteor 2.13 | How to migrate your application to Meteor 2.13. |
Most of the new features in Meteor 2.13 are either applied directly behind the scenes (in a backwards compatible manner) or are opt-in. For a complete breakdown of the changes, please refer to the changelog.
In order to correctly run projects in Meteor 2.13 with Docker, you will need to update your Dockerfile to use our Docker image that contains Nodejs v14.21.4.
If you are using Meteor Cloud default base image, you don't need to change anything. If you are using a custom image, please update it accordingly to use the docker image provided or make sure you are using our Node.js 14.21.4 with the security updates.
Migrating from a version older than 2.12?
If you're migrating from a version of Meteor older than Meteor 2.12, there may be important considerations not listed in this guide. Please review the older migration guides for details:
- Migrating to Meteor 2.12 (from 2.11)
- Migrating to Meteor 2.11 (from 2.10)
- Migrating to Meteor 2.10 (from 2.9)
- Migrating to Meteor 2.9 (from 2.8)
- Migrating to Meteor 2.8 (from 2.7)
- Migrating to Meteor 2.7 (from 2.6)
- Migrating to Meteor 2.6 (from 2.5)
- Migrating to Meteor 2.5 (from 2.4)
- Migrating to Meteor 2.4 (from 2.3)
- Migrating to Meteor 2.3 (from 2.2)
- Migrating to Meteor 2.2 (from 2.0)
- Migrating to Meteor 2.0 (from 1.12)
- Migrating to Meteor 1.12 (from 1.11)
- Migrating to Meteor 1.11 (from 1.10.2)
- Migrating to Meteor 1.10.2 (from 1.10)
- Migrating to Meteor 1.10 (from 1.9.3)
- Migrating to Meteor 1.9.3 (from 1.9)
- Migrating to Meteor 1.9 (from 1.8.3)
- Migrating to Meteor 1.8.3 (from 1.8.2)
- Migrating to Meteor 1.8.2 (from 1.8)
- Migrating to Meteor 1.8 (from 1.7)
- Migrating to Meteor 1.7 (from 1.6)
- Migrating to Meteor 1.6 (from 1.5)
- Migrating to Meteor 1.5 (from 1.4)
- Migrating to Meteor 1.4 (from 1.3)
- Migrating to Meteor 1.3 (from 1.2)