Skip to content

Commit

Permalink
NO-REF: Updating release notes
Browse files Browse the repository at this point in the history
  • Loading branch information
kylevillegas93 committed Oct 31, 2024
1 parent ee85835 commit 92cef72
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -177,7 +177,7 @@ We use git tags to tag releases and github's release feature to deploy. The ste
7. In github, navigate to the 'Releases' tab and click on 'Draft a new release'
8. Choose to create a new tag (e.g. v0.12.0), set `main` as the target, and name your release after the new version number
('v0.12.0')
9. Summarize the changes in the release notes since the last deployment.
9. Use the following command to print out the release notes: `cat <(git log <first-commit>..HEAD --pretty=format:"%h - %s (%an, %ad)" --date=short)`. Replace `<first-commit>` with the SHA of the first commit.
10. Give the team a heads up in `#researchnow_aka_sfr` in Slack, make sure the release is 'Set as the latest release', and hit 'Publish release'
11. Check the repo's `Actions` tab to observe the progress of the deployment to production
- Note that the deployment job merely kicks off an ECS service update. To fully verify success, you'll need to check the
Expand Down

0 comments on commit 92cef72

Please sign in to comment.