Skip to content

create new release on deploy to production#1133

Merged
ajeety4 merged 2 commits into
mainfrom
ce-ay-sp/deploy-release-updates
May 18, 2026
Merged

create new release on deploy to production#1133
ajeety4 merged 2 commits into
mainfrom
ce-ay-sp/deploy-release-updates

Conversation

@calellowitz
Copy link
Copy Markdown
Collaborator

@calellowitz calellowitz commented Apr 21, 2026

Technical Summary

This updates the deploy workflow to create a release automatically when deploying to production

Safety Assurance

Safety story

deploy workflow only

QA Plan

Tested on staging

Labels & Review

  • The set of people pinged as reviewers is appropriate for the level of risk of the change

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 21, 2026

Review Change Stack
No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9ab82973-69a7-4b17-8f99-4c2bf884b49a

📥 Commits

Reviewing files that changed from the base of the PR and between bd855c0 and 5a90805.

📒 Files selected for processing (1)
  • .github/workflows/deploy.yml
🚧 Files skipped from review as they are similar to previous changes (1)
  • .github/workflows/deploy.yml

Walkthrough

The deploy GitHub Actions workflow now grants the GITHUB_TOKEN write access to repository contents and, on successful production runs, sets RELEASE_TAG to a UTC timestamp (YYYY-MM-DD_HH-MM-SS) and creates a GitHub Release using that tag/name targeting github.sha with generated release notes. These steps run after Sentry release creation; the Slack notify step still runs with if: always().

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: adding automatic release creation to the production deployment workflow.
Description check ✅ Passed The description is related to the changeset and explains that the deploy workflow was updated to create releases automatically when deploying to production.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ce-ay-sp/deploy-release-updates

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

tag_name: ${{ env.RELEASE_DATE }}
name: ${{ env.RELEASE_DATE }}
target_commitish: ${{ github.sha }}
generate_release_notes: true
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does this do? List all PRs and descriptions?

Copy link
Copy Markdown
Collaborator Author

@calellowitz calellowitz Apr 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, its the same thing that currently happens when you press the button manually. Its a builtin github option

Comment thread .github/workflows/deploy.yml Outdated
if: ${{ success() && inputs.environment == 'production' }}
uses: softprops/action-gh-release@v2
with:
tag_name: ${{ env.RELEASE_DATE }}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what happens if there are two deploys on the same day?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a great question, this step would probably fail. I think that's a pretty rare occurrence, but not impossible. HQ uses the time as well. That would be easy to add

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so you want to add that or use just the date?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry took a while, but did update the tag. feel free to review again

@ajeety4 ajeety4 merged commit 5ba27c2 into main May 18, 2026
7 checks passed
@ajeety4 ajeety4 deleted the ce-ay-sp/deploy-release-updates branch May 18, 2026 09:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants