🌝Deploying to Production
Last updated
Last updated
We merge all reviewed and approved PR's to main
and then merge to the production
branch to start the automated deployment process.
Pull Requests
*cal.vercel.app
Preview
main
app.cal.dev
Staging
production
app.cal.com
Production
Bump "version" in apps/web/package.json
according to semver standards, stage it in git and "Commit changes" directly to the main
branch.
Create a new release in GitHub: https://github.com/calcom/cal.com/releases/new
Type the new version and hit "Create new tag: vX.Y.Z on publish"
Use the "Create auto generated release text" button
Publish release
Profit!
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):