Skip to content

Latest commit

 

History

History
52 lines (38 loc) · 2.06 KB

releasing.md

File metadata and controls

52 lines (38 loc) · 2.06 KB
Raw

Releases and deployment

Releases and changelogs are automatically generated using standard-version. To generate a new release run:

npm run release

This will:

  • update contributors in package.json
  • increase the version in package.json based on commits since last tag
  • create a new changelog entry
  • create a version commit
  • create a new git tag
  • push commit and tags to remote

Note: This will require your github user to be in a team with write access to the repo. If you do not see the Settings tab on the project you will need to contact a maintainer.

  • If you do not have the write permission, one of the steps of the deployment job will fail. This step can be manually repeated once the permission has been applied
  • ! [remote rejected]   HEAD -> main (protected branch hook declined)
error: failed to push some refs to 'github.com:ministryofjustice/hmpps-book-secure-move-frontend.git'

It will also start a new deployment specific job on CircleCI which will run the full suite of automated tests and create a release on GitHub.

Note: The deployment job has a manual approval step before it will release that version to production.

Clearing cached reference data

Sometimes, the need to clear cached reference data may arise - if a users locations have changed, for example. To clear cached reference data you can run with the following:

node tasks/clear-cache-reference-data.js DATA_NAME

OR

npm run clear-cache-reference-data -- DATA_NAME

DATA_NAME can be replaced with any reference data name, full list:

genders
ethnicities
assessment_questions
locations
regions
suppliers
prison_transfer_reasons
allocation_complex_cases
\*