[x] Create a branch for the release branch release-v1.4.0release-v1.3.1
[x] Update the dependencies. The dependabot PR backlog is not comprehensive and doesn't include transitive dependencies, and merging them one at a time tends to break things, so the best way to do this is manually with npm. commit 54a1db8a2d97754a6a0be9a54a74100133df284a
[x] Bump the intermineVersion in data-sources/intermine/api/index.ts if appropriate. N/A
[x] Update the base image version in the Dockerfile if necessary (this should be the most recent node LTS version) and do a test build and run of the Docker image on you local machine so you know if something is going to go off the rails before the automated build action on GitHub. N/A
[x] Update the GHCR image tag in compose.prod.yml to the imminent release version commit 9f43fd6dd34f5b7256e01bfb22202d2611f5a1c0
[x] Bump the "version" number in package.json. commit 9f43fd6dd34f5b7256e01bfb22202d2611f5a1c0
[x] Open a PR that merges the release branch into main. PR #151
[x] Merge the release PR after it passes testing and review.
[x] Tag a corresponding release on GitHub. This will trigger an automated Docker image build on GitHub. If the build succeeds it will be automatically published to GHCR.
alancleary
commented
6 months ago
release-v1.4.0release-v1.3.1intermineVersionindata-sources/intermine/api/index.tsif appropriate. N/ADockerfileif necessary (this should be the most recent node LTS version) and do a test build and run of the Docker image on you local machine so you know if something is going to go off the rails before the automated build action on GitHub. N/Acompose.prod.ymlto the imminent release version commit 9f43fd6dd34f5b7256e01bfb22202d2611f5a1c0"version"number inpackage.json. commit 9f43fd6dd34f5b7256e01bfb22202d2611f5a1c0