🌝Deploying to Production

We merge all reviewed and approved PR's to main and then merge to the production branch to start the automated deployment process.

Branch
Deployed
Envirorment

Pull Requests

*cal.vercel.app

Preview

main

app.cal.dev

Staging

production

app.cal.com

Production

Steps to release a new version

  1. Bump "version" in apps/web/package.json according to semver standards, stage it in git and "Commit changes" directly to the main branch.

  2. Create a new release in GitHub: https://github.com/calcom/cal.com/releases/new

  3. Type the new version and hit "Create new tag: vX.Y.Z on publish"

  4. Use the "Create auto generated release text" button

  5. Publish release

  6. Profit!

Check for migrations

This is important. When doing a release make sure you run proper migrations first.

Also, important sidenote, if a migration is adding a new table. We need to re-grant proper permissions to each created username that are currently being used. Run these commands for each username (Replcing <USERNAME> with the proper one):

GRANT ALL PRIVILEGES ON ALL SEQUENCES IN SCHEMA public TO <USERNAME>;
GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA public TO <USERNAME>;

Last updated

Was this helpful?