This PR addresses an issue where the deployment helper script was not returning the correct commitId during the release process. The script has been updated to accurately retrieve and return the commitId associated with the current release.
Updates the logic in scripts/release-helper.py See line 58
Steps to Test
Notes
Code author checklist
[X] I have rebased this branch from the latest main branch
[X] I have performed a self-review of my code
[X] I have created and/or updated relevant documentation on the engineering documentation website
[X] I have not used any relative imports
[X] I have pruned any instances of unused code
[X] I have not added any markdown to labels, titles and button text in config
[X] If I added/updated any values in userData (including profileData, formationData etc), then I added a new migration file
[X] I have checked for and removed instances of unused config from CMS
[X] If I added any new collections to the CMS config, then I updated the search tool and cmsCollections.ts (see CMS Additions in Engineering Reference/FAQ on the engineering documentation site)
[X] I have updated relevant .env values in both .env-template and in Bitwarden
Description
This PR addresses an issue where the deployment helper script was not returning the correct
commitIdduring the release process. The script has been updated to accurately retrieve and return thecommitIdassociated with the current release.Ticket
This pull request resolves #188213387.
Approach
scripts/release-helper.pySee line 58Steps to Test
Notes
Code author checklist
userData(includingprofileData,formationDataetc), then I added a new migration filecmsCollections.ts(see CMS Additions in Engineering Reference/FAQ on the engineering documentation site).envvalues in both.env-templateand in Bitwarden