From f5644a322ebd97965c34d01bca5d385861640818 Mon Sep 17 00:00:00 2001 From: Jonathan Cameron Date: Tue, 12 Mar 2024 16:42:19 -0400 Subject: [PATCH] Updated --- RELEASES.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/RELEASES.md b/RELEASES.md index 46965acb97..7f0238afd0 100644 --- a/RELEASES.md +++ b/RELEASES.md @@ -18,14 +18,15 @@ The directions below assume you are working in a development environment based o 9. Move the `server/models/migrations/next/migrate.sql` file to the directory created in the previous step. 10. Create an empty `migrate.sql` file in `server/models/migrations/next/`. You may insert a comment at the top of the file including the name of the new release version. 11. Commit any updated files (`git commit ...`) -12. Push your branch to the BHIMA upstream repo and make a PR: +12. Push your branch to the BHIMA upstream repo: - `git push --set-upstream upstream release-next` -13. Make sure your personal GITHUB_TOKEN environment variable is defined +13. In github, convert your branch to a PR in the `IMA-WorldHealth/bhima` repository. +14. Make sure your personal GITHUB_TOKEN environment variable is defined (assuming you have permissions to update the main BHIMA repository. [See Github instructions for this.](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens) -14. Run `yarn release` and follow the directions. -15. Verify the release was created and that the binary .tar.gz file +15. Run `yarn release` and follow the directions. +16. Verify the release was created and that the binary .tar.gz file is in the assets for the release. -16. Via the github interface, merge your `release-next` PR into `master` +17. Via the github interface, merge your `release-next` PR into `master` (*) Optional, Best Practice: Test the latest database changes on a production database.