From 8e684c26f1dc9a546a1f1a1e8634d6229b2e5158 Mon Sep 17 00:00:00 2001 From: Russ Poetker Date: Wed, 31 Jul 2024 13:24:27 -0400 Subject: [PATCH 1/2] Add release actions page --- docs/release/release-actions-1.9.0.md | 39 +++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 docs/release/release-actions-1.9.0.md diff --git a/docs/release/release-actions-1.9.0.md b/docs/release/release-actions-1.9.0.md new file mode 100644 index 0000000..870f89c --- /dev/null +++ b/docs/release/release-actions-1.9.0.md @@ -0,0 +1,39 @@ +# Release Manager Actions Checklist Template + +| | | +| --- |-----------------| +| Release version | 1.9.0 | +| Next dev version | 1.10.0-SNAPSHOT | + +## Release Process Overview +This is the full detailed release process, including the steps that are performed by the GitHub automation: [Release](../dev/release.md) + +## Pre-release + +- [x] Identify the version to be utilized for the release. +- [x] Ensure all code commits and PRs intended for the release have been merged. +- [x] Issue a code freeze statement on the Eclipse PASS slack #pass-dev channel to notify all developers that a release is imminent. + +[Release Steps with Automations](../dev/release-steps-with-automations.md) + +## Release Projects + +[Release All Modules Workflow](https://github.com/eclipse-pass/main/actions/workflows/pass-complete-release.yml) + +- [x] Release Main +- [x] Release Pass-Core +- [x] Release Pass Support +- [x] Release Pass UI +- [x] Release Pass Acceptance Testing +- [x] Release Pass Docker + +## Post-release + +- [x] Test the release by using the [acceptance test workflow](https://github.com/eclipse-pass/pass-acceptance-testing/actions/workflows/test.yml). Enter the release number into the Ref field. +- [x] Check that correct tickets are in the release milestone. [GitHub Ticket Update](../dev/release.md#update-release-notes) +- [x] Write release notes in the [Release Notes doc](../release-notes.md), submit a PR for the changes, and ensure the PR is merged. Release Notes should be written to be understandable by community members who are not technical. +- [x] Draft release message and have technical & community lead provide feedback. Ensure that a link to the release notes is included in the release message. +- [x] Post a message about the release to the PASS Google Group. [Notes about the PASS Google Group](../dev/release.md#process) +- [x] Update template if any steps were missed or if any new tasks were added. Also make note of these new steps in the release-actions-X.X.X.md file. +- [x] Update [Pass Demo](https://demo.eclipse-pass.org) to new release - [Publish to SNS Topic action](https://github.com/eclipse-pass/main/actions/workflows/deployToAWS.yml) using `Environment: demo` +- [x] Send message to Eclipse PASS slack #pass-dev channel that the release is complete. From 2f108ba323c09d22826094d30b49f89932d08b10 Mon Sep 17 00:00:00 2001 From: Russ Poetker Date: Thu, 1 Aug 2024 10:51:28 -0400 Subject: [PATCH 2/2] Always build node build production mode --- .github/actions/node-build/action.yml | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/.github/actions/node-build/action.yml b/.github/actions/node-build/action.yml index 07a321f..72dc342 100644 --- a/.github/actions/node-build/action.yml +++ b/.github/actions/node-build/action.yml @@ -30,9 +30,5 @@ runs: run: | export $(grep -v '^[#|SIGNING|PASS_CORE_POLICY]' $ENV_FILE_PATH | xargs -d '\n') pnpm install --frozen-lockfile - if [ "$IS_DEV" == "true" ]; then - pnpm run build:dev - else - pnpm run build - fi + pnpm run build pnpm run build:docker