Skip to main content

Upgrading

  • Get the newest version from the changelog page.
  • Upgrade all packages to the newest version (@remotion/lambda, but also remotion, @remotion/cli etc.)
- "@remotion/bundler": "^2.4.1"
+ "@remotion/bundler": "3.0.0-alpha.b886f9bc"

- "@remotion/renderer": "^2.4.1"
+ "@remotion/renderer": "3.0.0-alpha.b886f9bc"

- "remotion": "^2.4.1"
+ "remotion": "3.0.0-alpha.b886f9bc"
  • (Optional): Remove the old versions of the function:
info

You only should do this if the function is not being used anymore. If you are still using it in production, you can just skip this step.

npx remotion lambda functions rmall -y
npx remotion lambda functions rmall -y
  • Deploy the newest version of the Remotion Lambda function:
npx remotion lambda functions deploy
npx remotion lambda functions deploy
  • Update your API calls according to the changelog. While Remotion Lambda is in Alpha, breaking changes may occur in every version. Once it hits stable, breaking changes will only occur in major version bumps.

Separating production and testing environments​

If you already shipped Remotion Lambda to production, you can upgrade without incurring any downtime. Each version of Remotion Lambda has a schema identifier (in the format of 2021-08-12) that will increment whenever Remotion Lambda gets upgraded.

If you have Remotion in production and cloned locally, upgrading Remotion Lambda in your code locally and then rendering a video will yield an error message that the versions are mismatching. Simply deploy a new function npx remotion lambda functions deploy and your local environment will talk to the new function, while production will talk to the older function.

If everything works and you commit and deploy the change to production, it will start talking to the new version and you can safely remove the old function.