From 179612b8b4c9b7e5ab98b07b7781f671e1127d6f Mon Sep 17 00:00:00 2001 From: rpoet-jh Date: Wed, 31 Jul 2024 12:47:13 +0000 Subject: [PATCH 01/26] Update version to 1.9.0 --- pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index 7aa8e13..c62007d 100644 --- a/pom.xml +++ b/pom.xml @@ -4,7 +4,7 @@ org.eclipse.pass eclipse-pass-parent - 1.9.0-SNAPSHOT + 1.9.0 pom Eclipse-PASS Parent From a29a3bde0ab4c2cd726e67749f2b06c57871b750 Mon Sep 17 00:00:00 2001 From: rpoet-jh Date: Wed, 31 Jul 2024 13:43:22 +0000 Subject: [PATCH 02/26] Update version to 1.10.0-SNAPSHOT --- pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index c62007d..d46816c 100644 --- a/pom.xml +++ b/pom.xml @@ -4,7 +4,7 @@ org.eclipse.pass eclipse-pass-parent - 1.9.0 + 1.10.0-SNAPSHOT pom Eclipse-PASS Parent From dfc876d31555314460928a2fc7274de3ad71f38f Mon Sep 17 00:00:00 2001 From: Russ Poetker Date: Wed, 31 Jul 2024 10:20:41 -0400 Subject: [PATCH 03/26] Update node ghwf actions for pnpm --- .../{yarn-build => node-build}/action.yml | 18 +++++++++++------- .../{yarn-version => node-version}/action.yml | 18 +++++++++++------- .github/workflows/pass-complete-release.yml | 18 +++++++++--------- 3 files changed, 31 insertions(+), 23 deletions(-) rename .github/actions/{yarn-build => node-build}/action.yml (67%) rename .github/actions/{yarn-version => node-version}/action.yml (55%) diff --git a/.github/actions/yarn-build/action.yml b/.github/actions/node-build/action.yml similarity index 67% rename from .github/actions/yarn-build/action.yml rename to .github/actions/node-build/action.yml index 51b0440..07a321f 100644 --- a/.github/actions/yarn-build/action.yml +++ b/.github/actions/node-build/action.yml @@ -1,6 +1,6 @@ -name: Build yarn module for release +name: Build package module for release description: | - Build yarn module + Build package module inputs: repository_dir: @@ -17,7 +17,11 @@ inputs: runs: using: composite steps: - - name: Builds yarn module + - name: Install pnpm + uses: pnpm/action-setup@v4 + with: + version: 9 + - name: Builds module shell: bash working-directory: ${{ inputs.repository_dir }} env: @@ -25,10 +29,10 @@ runs: IS_DEV: ${{ inputs.is_dev }} run: | export $(grep -v '^[#|SIGNING|PASS_CORE_POLICY]' $ENV_FILE_PATH | xargs -d '\n') - yarn install --frozen-lockfile + pnpm install --frozen-lockfile if [ "$IS_DEV" == "true" ]; then - yarn run build:dev + pnpm run build:dev else - yarn run build + pnpm run build fi - yarn run build:docker + pnpm run build:docker diff --git a/.github/actions/yarn-version/action.yml b/.github/actions/node-version/action.yml similarity index 55% rename from .github/actions/yarn-version/action.yml rename to .github/actions/node-version/action.yml index 12a9c28..f1d61f3 100644 --- a/.github/actions/yarn-version/action.yml +++ b/.github/actions/node-version/action.yml @@ -1,6 +1,6 @@ -name: Update yarn version for release +name: Update package version for release description: | - Updates yarn version which automatically does a commit and this action tags + Updates package version which automatically does a commit and this action tags inputs: repository_dir: @@ -14,17 +14,21 @@ inputs: runs: using: composite steps: - - name: Update yarn version and tag + - name: Install pnpm + uses: pnpm/action-setup@v4 + with: + version: 9 + - name: Update version and tag shell: bash working-directory: ${{ inputs.repository_dir }} env: SKIP_TAG: ${{ inputs.skip_tag }} run: | - yarn install --frozen-lockfile - yarn config set version-git-tag false - yarn version --new-version $RELEASE + pnpm install --frozen-lockfile + pnpm config set version-git-tag false + pnpm version --new-version $RELEASE git commit --allow-empty -am "Update version to $RELEASE" if [ "$SKIP_TAG" == "false" ]; then - echo "Tagging yarn version $RELEASE" + echo "Tagging version $RELEASE" git tag $RELEASE fi diff --git a/.github/workflows/pass-complete-release.yml b/.github/workflows/pass-complete-release.yml index 762e6df..e476ca8 100644 --- a/.github/workflows/pass-complete-release.yml +++ b/.github/workflows/pass-complete-release.yml @@ -60,10 +60,10 @@ jobs: git clone https://${{ secrets.JAVA_RELEASE_PAT }}@github.com/eclipse-pass/pass-acceptance-testing.git combined/pass-acceptance-testing git clone https://${{ secrets.JAVA_RELEASE_PAT }}@github.com/eclipse-pass/pass-docker.git combined/pass-docker - - name: Setup Node & Yarn - uses: actions/setup-node@v3 + - name: Setup Node & pnpm + uses: actions/setup-node@v4 with: - node-version: 18 + node-version: 20 - name: Login to GHCR uses: docker/login-action@v2 @@ -166,7 +166,7 @@ jobs: - name: Set Release/commit/tag ~ pass-ui if: ${{ ! env.PASS_UI_TAG_EXISTS }} - uses: ./main/.github/actions/yarn-version + uses: ./main/.github/actions/node-version with: repository_dir: combined/pass-ui env: @@ -174,7 +174,7 @@ jobs: - name: Build Release pass-ui if: ${{ ! env.PASS_UI_TAG_EXISTS }} - uses: ./main/.github/actions/yarn-build + uses: ./main/.github/actions/node-build with: repository_dir: combined/pass-ui env_path: ../pass-docker/.env @@ -185,7 +185,7 @@ jobs: - name: Set Snapshot/commit ~ pass-ui if: ${{ ! env.PASS_UI_TAG_EXISTS }} - uses: ./main/.github/actions/yarn-version + uses: ./main/.github/actions/node-version with: repository_dir: combined/pass-ui skip_tag: "true" @@ -194,7 +194,7 @@ jobs: - name: Build Snapshot pass-ui if: ${{ ! env.PASS_UI_TAG_EXISTS }} - uses: ./main/.github/actions/yarn-build + uses: ./main/.github/actions/node-build with: repository_dir: combined/pass-ui env_path: ../pass-docker/.env @@ -217,7 +217,7 @@ jobs: - name: Set Release/commit/tag ~ pass-acceptance-testing if: ${{ ! env.PASS_ACCPT_TEST_TAG_EXISTS }} - uses: ./main/.github/actions/yarn-version + uses: ./main/.github/actions/node-version with: repository_dir: combined/pass-acceptance-testing env: @@ -225,7 +225,7 @@ jobs: - name: Set Snapshot/commit ~ pass-acceptance-testing if: ${{ ! env.PASS_ACCPT_TEST_TAG_EXISTS }} - uses: ./main/.github/actions/yarn-version + uses: ./main/.github/actions/node-version with: repository_dir: combined/pass-acceptance-testing skip_tag: "true" From ce4110d4f1b2ea26c16a3fa6808efdb14ba812ac Mon Sep 17 00:00:00 2001 From: Russ Poetker Date: Wed, 31 Jul 2024 10:46:15 -0400 Subject: [PATCH 04/26] Revert pass-acceptance-test step to use yarn --- .github/actions/yarn-version/action.yml | 30 +++++++++++++++++++++ .github/workflows/pass-complete-release.yml | 4 +-- 2 files changed, 32 insertions(+), 2 deletions(-) create mode 100644 .github/actions/yarn-version/action.yml diff --git a/.github/actions/yarn-version/action.yml b/.github/actions/yarn-version/action.yml new file mode 100644 index 0000000..195845a --- /dev/null +++ b/.github/actions/yarn-version/action.yml @@ -0,0 +1,30 @@ +name: Update yarn version for release +description: | + Updates yarn version which automatically does a commit and this action tags + +inputs: + repository_dir: + description: 'Directory of repository to update' + required: true + skip_tag: + description: 'Skip git tag' + required: false + default: "false" + +runs: + using: composite + steps: + - name: Update yarn version and tag + shell: bash + working-directory: ${{ inputs.repository_dir }} + env: + SKIP_TAG: ${{ inputs.skip_tag }} + run: | + yarn install --frozen-lockfile + yarn config set version-git-tag false + yarn version --new-version $RELEASE + git commit --allow-empty -am "Update version to $RELEASE" + if [ "$SKIP_TAG" == "false" ]; then + echo "Tagging yarn version $RELEASE" + git tag $RELEASE + fi \ No newline at end of file diff --git a/.github/workflows/pass-complete-release.yml b/.github/workflows/pass-complete-release.yml index e476ca8..44dae70 100644 --- a/.github/workflows/pass-complete-release.yml +++ b/.github/workflows/pass-complete-release.yml @@ -217,7 +217,7 @@ jobs: - name: Set Release/commit/tag ~ pass-acceptance-testing if: ${{ ! env.PASS_ACCPT_TEST_TAG_EXISTS }} - uses: ./main/.github/actions/node-version + uses: ./main/.github/actions/yarn-version with: repository_dir: combined/pass-acceptance-testing env: @@ -225,7 +225,7 @@ jobs: - name: Set Snapshot/commit ~ pass-acceptance-testing if: ${{ ! env.PASS_ACCPT_TEST_TAG_EXISTS }} - uses: ./main/.github/actions/node-version + uses: ./main/.github/actions/yarn-version with: repository_dir: combined/pass-acceptance-testing skip_tag: "true" From a425a918e85d8352392145d2f45e5b2842e37f33 Mon Sep 17 00:00:00 2001 From: Russ Poetker Date: Wed, 31 Jul 2024 11:44:20 -0400 Subject: [PATCH 05/26] Add 1.9.0 release notes --- docs/release-notes.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs/release-notes.md b/docs/release-notes.md index fbec618..ad6e64c 100644 --- a/docs/release-notes.md +++ b/docs/release-notes.md @@ -1,3 +1,20 @@ +## Release v1.9.0 +### Date: July 31, 2024 + +Release Manager: Russ Poetker, JHU + +This release focused on improving deployment tests, addressing technical debt, and improving documentation. Deployment tests were updated to make deposits into downstream repositories optional. If a deployment test deposit is made into a downstream DSpace repository, it will be automatically deleted after the test completes. More deprecations in pass-ui were fixed which allowed pass-ui to be upgraded to Ember v5.8. The pass-ui module now uses Embroider and pnpm for building. The team continued work on overhauling the existing documentation. + +Tickets Completed: https://github.com/eclipse-pass/main/milestone/23?closed=1 + +Release Components: +* main - https://github.com/eclipse-pass/main/releases/tag/1.9.0 +* pass-core - https://github.com/eclipse-pass/pass-core/releases/tag/1.9.0 +* pass-docker - https://github.com/eclipse-pass/pass-docker/releases/tag/1.9.0 +* pass-acceptance-testing - https://github.com/eclipse-pass/pass-acceptance-testing/releases/tag/1.9.0 +* pass-support - https://github.com/eclipse-pass/pass-support/releases/tag/1.9.0 +* pass-ui - https://github.com/eclipse-pass/pass-ui/releases/tag/1.9.0 + ## Release v1.8.0 ### Date: July 1, 2024 From 3455b375823b7f42635185e1a00d206cf4bb09db Mon Sep 17 00:00:00 2001 From: Russ Poetker Date: Wed, 31 Jul 2024 13:24:27 -0400 Subject: [PATCH 06/26] 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 337fbc1b286126700fee7113e95b836c8aaaead4 Mon Sep 17 00:00:00 2001 From: Russ Poetker Date: Thu, 1 Aug 2024 10:51:28 -0400 Subject: [PATCH 07/26] 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 From 98ff5d2e7277bdc843e164a70ad63efa42f5ab36 Mon Sep 17 00:00:00 2001 From: rpoet-jh Date: Thu, 1 Aug 2024 15:29:38 +0000 Subject: [PATCH 08/26] Update version to 1.9.1 --- pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index d46816c..110a29b 100644 --- a/pom.xml +++ b/pom.xml @@ -4,7 +4,7 @@ org.eclipse.pass eclipse-pass-parent - 1.10.0-SNAPSHOT + 1.9.1 pom Eclipse-PASS Parent From f0c5c14bc3a76697e28284ab20d7dc22d8a19dcd Mon Sep 17 00:00:00 2001 From: rpoet-jh Date: Thu, 1 Aug 2024 16:13:49 +0000 Subject: [PATCH 09/26] Update version to 1.10.0-SNAPSHOT --- pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index 110a29b..d46816c 100644 --- a/pom.xml +++ b/pom.xml @@ -4,7 +4,7 @@ org.eclipse.pass eclipse-pass-parent - 1.9.1 + 1.10.0-SNAPSHOT pom Eclipse-PASS Parent From 8abb32c4169fedd46ed7fc6f91be615ef9c4881e Mon Sep 17 00:00:00 2001 From: Russ Poetker Date: Thu, 1 Aug 2024 13:18:41 -0400 Subject: [PATCH 10/26] Add 1.9.1 release notes --- docs/release-notes.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs/release-notes.md b/docs/release-notes.md index ad6e64c..e5de1a1 100644 --- a/docs/release-notes.md +++ b/docs/release-notes.md @@ -1,3 +1,20 @@ +## Release v1.9.1 +### Date: August 1, 2024 + +Release Manager: Russ Poetker, JHU + +This release fixes a bug with the layout of some of the pages in the UI. + +Tickets Completed: https://github.com/eclipse-pass/main/milestone/25?closed=1 + +Release Components: +* main - https://github.com/eclipse-pass/main/releases/tag/1.9.1 +* pass-core - https://github.com/eclipse-pass/pass-core/releases/tag/1.9.1 +* pass-docker - https://github.com/eclipse-pass/pass-docker/releases/tag/1.9.1 +* pass-acceptance-testing - https://github.com/eclipse-pass/pass-acceptance-testing/releases/tag/1.9.1 +* pass-support - https://github.com/eclipse-pass/pass-support/releases/tag/1.9.1 +* pass-ui - https://github.com/eclipse-pass/pass-ui/releases/tag/1.9.1 + ## Release v1.9.0 ### Date: July 31, 2024 From 20649715687adb6df40515aca5c2e5ec74c83388 Mon Sep 17 00:00:00 2001 From: Russ Poetker Date: Thu, 1 Aug 2024 13:44:04 -0400 Subject: [PATCH 11/26] Add 1.9.1 release actions --- docs/release/release-actions-1.9.1.md | 39 +++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 docs/release/release-actions-1.9.1.md diff --git a/docs/release/release-actions-1.9.1.md b/docs/release/release-actions-1.9.1.md new file mode 100644 index 0000000..695444c --- /dev/null +++ b/docs/release/release-actions-1.9.1.md @@ -0,0 +1,39 @@ +# Release Manager Actions Checklist Template + +| | | +| --- |-----------------| +| Release version | 1.9.1 | +| 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 0d0e82c57541b19649c8b0f8124ab2a9d3444e57 Mon Sep 17 00:00:00 2001 From: Russ Poetker Date: Fri, 2 Aug 2024 13:25:23 -0400 Subject: [PATCH 12/26] Use git-tag-version flag on pnpm version command --- .github/actions/node-version/action.yml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/.github/actions/node-version/action.yml b/.github/actions/node-version/action.yml index f1d61f3..fad89dd 100644 --- a/.github/actions/node-version/action.yml +++ b/.github/actions/node-version/action.yml @@ -25,8 +25,7 @@ runs: SKIP_TAG: ${{ inputs.skip_tag }} run: | pnpm install --frozen-lockfile - pnpm config set version-git-tag false - pnpm version --new-version $RELEASE + pnpm version --git-tag-version false --new-version $RELEASE git commit --allow-empty -am "Update version to $RELEASE" if [ "$SKIP_TAG" == "false" ]; then echo "Tagging version $RELEASE" From cb07d60e42fa78792803960438e41ba48e513fbe Mon Sep 17 00:00:00 2001 From: rpoet-jh Date: Wed, 28 Aug 2024 12:45:16 +0000 Subject: [PATCH 13/26] Update version to 1.10.0 --- pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index d46816c..82bf600 100644 --- a/pom.xml +++ b/pom.xml @@ -4,7 +4,7 @@ org.eclipse.pass eclipse-pass-parent - 1.10.0-SNAPSHOT + 1.10.0 pom Eclipse-PASS Parent From 1d18469087a2c491a614a1819ce40a0aabaf638f Mon Sep 17 00:00:00 2001 From: rpoet-jh Date: Wed, 28 Aug 2024 13:42:02 +0000 Subject: [PATCH 14/26] Update version to 1.11.0-SNAPSHOT --- pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index 82bf600..fd964ad 100644 --- a/pom.xml +++ b/pom.xml @@ -4,7 +4,7 @@ org.eclipse.pass eclipse-pass-parent - 1.10.0 + 1.11.0-SNAPSHOT pom Eclipse-PASS Parent From 562172383b9890bf97d0c450f1b46a43500ff64c Mon Sep 17 00:00:00 2001 From: Russ Poetker Date: Wed, 28 Aug 2024 10:35:35 -0400 Subject: [PATCH 15/26] Add 1.10.0 release notes --- docs/release-notes.md | 17 +++++++++++++++++ docs/release/release-actions-1.10.0.md | 3 +++ 2 files changed, 20 insertions(+) create mode 100644 docs/release/release-actions-1.10.0.md diff --git a/docs/release-notes.md b/docs/release-notes.md index e5de1a1..65b1a55 100644 --- a/docs/release-notes.md +++ b/docs/release-notes.md @@ -1,3 +1,20 @@ +## Release v1.10.0 +### Date: August 28, 2024 + +Release Manager: Russ Poetker, JHU + +This release focused on a new Deposit Services repository integration, NIHMS Data Loader automation, and Release process and Documentation improvements. Deposit services has been enhanced to be able to deposit into InvenioRDM. This can also be tested locally with pass-docker being able to start a local instance of InvenioRDM. There is a new automation available in NIHMS Data Loader for refreshing the NIHMS API Token. We made a change to the pass-core/pass-support releases to align the maven repackage plugin configuration with its latest recommendations. As part of this change, the repackaged jar file is no longer deployed to Maven Central during release. The team continued work on overhauling and improving the existing documentation. + +Tickets Completed: https://github.com/eclipse-pass/main/milestone/24?closed=1 + +Release Components: +* main - https://github.com/eclipse-pass/main/releases/tag/1.10.0 +* pass-core - https://github.com/eclipse-pass/pass-core/releases/tag/1.10.0 +* pass-docker - https://github.com/eclipse-pass/pass-docker/releases/tag/1.10.0 +* pass-acceptance-testing - https://github.com/eclipse-pass/pass-acceptance-testing/releases/tag/1.10.0 +* pass-support - https://github.com/eclipse-pass/pass-support/releases/tag/1.10.0 +* pass-ui - https://github.com/eclipse-pass/pass-ui/releases/tag/1.10.0 + ## Release v1.9.1 ### Date: August 1, 2024 diff --git a/docs/release/release-actions-1.10.0.md b/docs/release/release-actions-1.10.0.md new file mode 100644 index 0000000..2a500dc --- /dev/null +++ b/docs/release/release-actions-1.10.0.md @@ -0,0 +1,3 @@ +# Release Manager Actions Checklist Template + +- Release tracked in GitHub issue: https://github.com/eclipse-pass/main/issues/1039 From 1b703cfc5f5f7a9d34039f3b49893074604e0ee7 Mon Sep 17 00:00:00 2001 From: Russ Poetker Date: Thu, 29 Aug 2024 16:09:05 -0400 Subject: [PATCH 16/26] Push nihms token refresh image in release all wf --- .github/workflows/pass-complete-release.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/workflows/pass-complete-release.yml b/.github/workflows/pass-complete-release.yml index 44dae70..5881bd5 100644 --- a/.github/workflows/pass-complete-release.yml +++ b/.github/workflows/pass-complete-release.yml @@ -115,6 +115,7 @@ jobs: docker push ghcr.io/eclipse-pass/jhu-grant-loader:$RELEASE docker push ghcr.io/eclipse-pass/pass-journal-loader:$RELEASE docker push ghcr.io/eclipse-pass/pass-nihms-loader:$RELEASE + docker push ghcr.io/eclipse-pass/pass-nihms-token-refresh:$RELEASE - name: Set Snapshot/commit ~ Java Repositories if: ${{ ! env.ALL_JAVA_REPOS_TAG_EXISTS }} @@ -143,6 +144,7 @@ jobs: docker push ghcr.io/eclipse-pass/jhu-grant-loader:$NEXT docker push ghcr.io/eclipse-pass/pass-journal-loader:$NEXT docker push ghcr.io/eclipse-pass/pass-nihms-loader:$NEXT + docker push ghcr.io/eclipse-pass/pass-nihms-token-refresh:$NEXT - name: Push the commits and tags ~ Java Repositories if: ${{ ! env.ALL_JAVA_REPOS_TAG_EXISTS }} From de2018560410ffcbaab5ad3079d3c6cfa64aeeaa Mon Sep 17 00:00:00 2001 From: Mark Patton Date: Fri, 6 Sep 2024 10:47:38 -0400 Subject: [PATCH 17/26] Remove no longer needed steps to build custom ldap and idp images from the release workflow --- .github/workflows/pass-complete-release.yml | 22 --------------------- 1 file changed, 22 deletions(-) diff --git a/.github/workflows/pass-complete-release.yml b/.github/workflows/pass-complete-release.yml index 5881bd5..87ad357 100644 --- a/.github/workflows/pass-complete-release.yml +++ b/.github/workflows/pass-complete-release.yml @@ -253,17 +253,6 @@ jobs: git commit --allow-empty -am "Update version to $RELEASE" git tag --force $RELEASE - - name: Build Release pass-docker images - if: ${{ ! env.PASS_DOCKER_TAG_EXISTS }} - working-directory: combined/pass-docker - run: docker compose -f docker-compose.yml -f eclipse-pass.local.yml build idp ldap - - - name: Push Release Docker images to GHCR ~ pass-docker - if: ${{ ! env.PASS_DOCKER_TAG_EXISTS }} - run: | - docker push ghcr.io/eclipse-pass/demo-ldap:$RELEASE - docker push ghcr.io/eclipse-pass/idp:$RELEASE - - name: Set Snapshot/commit ~ pass-docker if: ${{ ! env.PASS_DOCKER_TAG_EXISTS }} run: | @@ -271,17 +260,6 @@ jobs: sed -i "/^PASS_VERSION/s/.*/PASS_VERSION=$NEXT/" .env git commit --allow-empty -am "Update version to $NEXT" - - name: Build Snapshot pass-docker images - if: ${{ ! env.PASS_DOCKER_TAG_EXISTS }} - working-directory: combined/pass-docker - run: docker compose -f docker-compose.yml -f eclipse-pass.local.yml build idp ldap - - - name: Push Snapshot Docker images to GHCR ~ pass-docker - if: ${{ ! env.PASS_DOCKER_TAG_EXISTS }} - run: | - docker push ghcr.io/eclipse-pass/demo-ldap:$NEXT - docker push ghcr.io/eclipse-pass/idp:$NEXT - - name: Push the commits and tags ~ pass-docker if: ${{ ! env.PASS_DOCKER_TAG_EXISTS }} run: cd combined/pass-docker && git push --atomic origin main --force $RELEASE From 35b41027f86467db03749986b4ca3e85baa8ba94 Mon Sep 17 00:00:00 2001 From: Timothy Sanders Date: Thu, 12 Sep 2024 16:53:40 -0400 Subject: [PATCH 18/26] Add bug-fix-issue.md --- .github/ISSUE_TEMPLATE/bug-fix-issue.md | 47 +++++++++++++++++++++++++ 1 file changed, 47 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/bug-fix-issue.md diff --git a/.github/ISSUE_TEMPLATE/bug-fix-issue.md b/.github/ISSUE_TEMPLATE/bug-fix-issue.md new file mode 100644 index 0000000..b9b7a39 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug-fix-issue.md @@ -0,0 +1,47 @@ +--- +name: Bug Fix Issue +about: A standard Bug Fix template and the types of information that should be captured in a Bug Fix issue. +title: '' +labels: '' +assignees: '' + +--- + +# Prerequisites + +Please answer the following questions for yourself before submitting a Bug Fix issue: +* Is the title clear and understandable at a glance? +* Is a label present if appropriate? + +Labels are not required for all tickets, but they are helpful for prioritization. Please check the labels drop-down to see if any of the pre-set labels work for your ticket. + +**YOU SHOULD DELETE THE PREREQUISITES SECTION.** + +# Environment + +Indicate the environment that the bug was realized. This can also be more than environment. Can include the following: OS, browser, local/dev/staging/prod etc. + +# Date/time occurred + +Indicate the date/time the bug was realized. + +# Description + +What is the problem? What are the results? + +# Step to Reproduce + +What are the steps performed to reproduce this bug? + +# Expected Results + +What are the expected results? What is the expected behavior? + +# Evidence + +Please provide screenshots/screen capture or other evidence such as a log files (scrubbed of sensitive information). + +# Estimated Severity + +If possible, provide an initial estimate the severity of the issue. This of course can be adjusted after submission. + From 349abe79286c4722756a89b34d73ea4b8512f091 Mon Sep 17 00:00:00 2001 From: Timothy Sanders Date: Thu, 12 Sep 2024 16:58:43 -0400 Subject: [PATCH 19/26] Update Description section --- .github/ISSUE_TEMPLATE/bug-fix-issue.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/bug-fix-issue.md b/.github/ISSUE_TEMPLATE/bug-fix-issue.md index b9b7a39..601e48a 100644 --- a/.github/ISSUE_TEMPLATE/bug-fix-issue.md +++ b/.github/ISSUE_TEMPLATE/bug-fix-issue.md @@ -27,7 +27,7 @@ Indicate the date/time the bug was realized. # Description -What is the problem? What are the results? +What is the problem? What are the results? Describe what is currently happening in detail. # Step to Reproduce From 9b0878b84e65e2bce04939f103cffe2042f92f33 Mon Sep 17 00:00:00 2001 From: Timothy Sanders Date: Fri, 13 Sep 2024 16:42:38 -0400 Subject: [PATCH 20/26] Fix language --- .github/ISSUE_TEMPLATE/bug-fix-issue.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug-fix-issue.md b/.github/ISSUE_TEMPLATE/bug-fix-issue.md index 601e48a..c47a3d5 100644 --- a/.github/ISSUE_TEMPLATE/bug-fix-issue.md +++ b/.github/ISSUE_TEMPLATE/bug-fix-issue.md @@ -19,7 +19,7 @@ Labels are not required for all tickets, but they are helpful for prioritization # Environment -Indicate the environment that the bug was realized. This can also be more than environment. Can include the following: OS, browser, local/dev/staging/prod etc. +Indicate the environment that the bug was realized. This can also be more than environment and may include the following: OS, browser, local/dev/staging/prod etc. # Date/time occurred @@ -29,7 +29,7 @@ Indicate the date/time the bug was realized. What is the problem? What are the results? Describe what is currently happening in detail. -# Step to Reproduce +# Steps to Reproduce What are the steps performed to reproduce this bug? @@ -39,9 +39,9 @@ What are the expected results? What is the expected behavior? # Evidence -Please provide screenshots/screen capture or other evidence such as a log files (scrubbed of sensitive information). +Please provide screenshots/screen capture or other evidence such as log files (scrubbed of sensitive information). # Estimated Severity -If possible, provide an initial estimate the severity of the issue. This of course can be adjusted after submission. +If possible, provide an initial severity estimate of the issue. This of course can be adjusted after submission. From 3fb798c3ad36cf8f251fc9fc9fcc2e9f26769ef6 Mon Sep 17 00:00:00 2001 From: Timothy Sanders Date: Fri, 13 Sep 2024 17:01:59 -0400 Subject: [PATCH 21/26] Add enhancement-request-issue.md --- .../enhancement-request-issue.md | 42 +++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/enhancement-request-issue.md diff --git a/.github/ISSUE_TEMPLATE/enhancement-request-issue.md b/.github/ISSUE_TEMPLATE/enhancement-request-issue.md new file mode 100644 index 0000000..63ceaec --- /dev/null +++ b/.github/ISSUE_TEMPLATE/enhancement-request-issue.md @@ -0,0 +1,42 @@ +--- +name: Enhancement Request Issue +about: A standard Enhancement Request template and the types of information that should be captured in a Enhancement Request issue. +title: '' +labels: '' +assignees: '' + +--- + +# Prerequisites + +Please answer the following questions for yourself before submitting a Bug Fix issue: +* Is the title clear and understandable at a glance? +* Is a label present if appropriate? + +Labels are not required for all tickets, but they are helpful for prioritization. Please check the labels drop-down to see if any of the pre-set labels work for your ticket. + +**YOU SHOULD DELETE THE PREREQUISITES SECTION.** + +# Description + +A description of the enhancement. + +# Value + +Why is this enhancement important/valuable? + +# Users/Target Audience + +Who would benefit from this enhancement? + +# Requirements + +If known, what are the dependencies and infrastructure required for this enhancement? + +# Examples + +Are there any current examples of this feature somewhere else? Please provide screenshots or URLs of this enhancement. + +# Risks + +Are there any risks that may be associated with this enhancement? For example, cost, time, performance impact or increased complexity? \ No newline at end of file From 35d6731ba4131d7f320bc651ad7847db273ac66b Mon Sep 17 00:00:00 2001 From: Timothy Sanders Date: Fri, 13 Sep 2024 17:09:36 -0400 Subject: [PATCH 22/26] Add release-checklist-issue.md --- .../ISSUE_TEMPLATE/release-checklist-issue.md | 47 +++++++++++++++++++ 1 file changed, 47 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/release-checklist-issue.md diff --git a/.github/ISSUE_TEMPLATE/release-checklist-issue.md b/.github/ISSUE_TEMPLATE/release-checklist-issue.md new file mode 100644 index 0000000..fab3fba --- /dev/null +++ b/.github/ISSUE_TEMPLATE/release-checklist-issue.md @@ -0,0 +1,47 @@ +--- +name: Release Checklist Issue +about: PASS Release Checklist includes all the necessary steps required to successfully release the next version of PASS. +title: 'Release MAJOR.MINOR.PATCH' +labels: 'Release' +assignees: '' + +--- + +# Release Manager Actions Checklist + +| | | +| --- |-----------------| +| Release version | MAJOR.MINOR.PATCH | +| Next dev version | MAJOR.MINOR.PATCH-SNAPSHOT | + +## Release Process Overview +This is the full detailed release process, including the steps that are performed by the GitHub automation: [Release](https://github.com/eclipse-pass/main/blob/main/docs/dev/release.md) + +## Pre-release + +- [] Identify the version to be utilized for the release. +- [] Ensure all code commits and PRs intended for the release have been merged. +- [] 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](https://github.com/eclipse-pass/main/blob/main/docs/dev/release-steps-with-automations.md) + +## Release Projects + +[Release All Modules Workflow](https://github.com/eclipse-pass/main/actions/workflows/pass-complete-release.yml) + +- [] Release Main +- [] Release Pass-Core +- [] Release Pass Support +- [] Release Pass UI +- [] Release Pass Acceptance Testing +- [] Release Pass Docker + +## Post-release + +- [] 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. +- [] Check that correct tickets are in the release milestone. [GitHub Ticket Update](https://github.com/eclipse-pass/main/blob/main/docs/dev/release.md#update-release-notes) +- [] Write release notes in the [Release Notes doc](https://github.com/eclipse-pass/main/blob/main/docs/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. +- [] Draft release message and have technical & community lead provide feedback. Ensure that a link to the release notes is included in the release message. +- [] Post a message about the release to the PASS Google Group. [Notes about the PASS Google Group](https://github.com/eclipse-pass/main/blob/main/docs/dev/release.md#process) +- [] 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` +- [] Send message to Eclipse PASS slack #pass-dev channel that the release is complete. \ No newline at end of file From 276f8b47e13ba2758ff43cb8ca2697e8e995e563 Mon Sep 17 00:00:00 2001 From: Timothy Sanders Date: Tue, 17 Sep 2024 09:26:44 -0400 Subject: [PATCH 23/26] Clean language --- .github/ISSUE_TEMPLATE/bug-fix-issue.md | 2 +- .github/ISSUE_TEMPLATE/release-checklist-issue.md | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug-fix-issue.md b/.github/ISSUE_TEMPLATE/bug-fix-issue.md index c47a3d5..aa53712 100644 --- a/.github/ISSUE_TEMPLATE/bug-fix-issue.md +++ b/.github/ISSUE_TEMPLATE/bug-fix-issue.md @@ -19,7 +19,7 @@ Labels are not required for all tickets, but they are helpful for prioritization # Environment -Indicate the environment that the bug was realized. This can also be more than environment and may include the following: OS, browser, local/dev/staging/prod etc. +Indicate the environment that the bug was realized. This can also be more than the environment and may include the following: OS, browser, local/dev/staging/prod etc. # Date/time occurred diff --git a/.github/ISSUE_TEMPLATE/release-checklist-issue.md b/.github/ISSUE_TEMPLATE/release-checklist-issue.md index fab3fba..87b9092 100644 --- a/.github/ISSUE_TEMPLATE/release-checklist-issue.md +++ b/.github/ISSUE_TEMPLATE/release-checklist-issue.md @@ -9,9 +9,9 @@ assignees: '' # Release Manager Actions Checklist -| | | -| --- |-----------------| -| Release version | MAJOR.MINOR.PATCH | +| | | +|------------------|----------------------------| +| Release version | MAJOR.MINOR.PATCH | | Next dev version | MAJOR.MINOR.PATCH-SNAPSHOT | ## Release Process Overview From 6ea03fc9c992638bc93fb30044982a43d39726bd Mon Sep 17 00:00:00 2001 From: Timothy Sanders Date: Tue, 17 Sep 2024 14:14:15 -0400 Subject: [PATCH 24/26] Update to language - Changes from the PASS Weekly meeting. --- .github/ISSUE_TEMPLATE/bug-fix-issue.md | 16 ++++++++++------ .../ISSUE_TEMPLATE/enhancement-request-issue.md | 8 ++++---- 2 files changed, 14 insertions(+), 10 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug-fix-issue.md b/.github/ISSUE_TEMPLATE/bug-fix-issue.md index aa53712..1da899d 100644 --- a/.github/ISSUE_TEMPLATE/bug-fix-issue.md +++ b/.github/ISSUE_TEMPLATE/bug-fix-issue.md @@ -1,17 +1,17 @@ --- -name: Bug Fix Issue -about: A standard Bug Fix template and the types of information that should be captured in a Bug Fix issue. +name: Bug Report Issue +about: A standard Bug Report template and the types of information that should be captured in a Bug Report issue. title: '' -labels: '' +labels: 'bug' assignees: '' --- # Prerequisites -Please answer the following questions for yourself before submitting a Bug Fix issue: +Please answer the following questions for yourself before submitting a Bug Report issue: * Is the title clear and understandable at a glance? -* Is a label present if appropriate? +* Should any other labels be added to this issue? Labels are not required for all tickets, but they are helpful for prioritization. Please check the labels drop-down to see if any of the pre-set labels work for your ticket. @@ -27,7 +27,7 @@ Indicate the date/time the bug was realized. # Description -What is the problem? What are the results? Describe what is currently happening in detail. +What is the problem? Describe what is currently happening in detail. # Steps to Reproduce @@ -37,6 +37,10 @@ What are the steps performed to reproduce this bug? What are the expected results? What is the expected behavior? +# Actual Results + +What are the actual results and provide any evidence of the actual results below. + # Evidence Please provide screenshots/screen capture or other evidence such as log files (scrubbed of sensitive information). diff --git a/.github/ISSUE_TEMPLATE/enhancement-request-issue.md b/.github/ISSUE_TEMPLATE/enhancement-request-issue.md index 63ceaec..4be3137 100644 --- a/.github/ISSUE_TEMPLATE/enhancement-request-issue.md +++ b/.github/ISSUE_TEMPLATE/enhancement-request-issue.md @@ -2,16 +2,16 @@ name: Enhancement Request Issue about: A standard Enhancement Request template and the types of information that should be captured in a Enhancement Request issue. title: '' -labels: '' +labels: 'Improvement' assignees: '' --- # Prerequisites -Please answer the following questions for yourself before submitting a Bug Fix issue: +Please answer the following questions for yourself before submitting an Enhancement Request issue: * Is the title clear and understandable at a glance? -* Is a label present if appropriate? +* Should any other labels be added to this issue? Labels are not required for all tickets, but they are helpful for prioritization. Please check the labels drop-down to see if any of the pre-set labels work for your ticket. @@ -19,7 +19,7 @@ Labels are not required for all tickets, but they are helpful for prioritization # Description -A description of the enhancement. +A description of the enhancement. What are the new features/improvements to this enhancement change? # Value From 08368625116104d6e2dbe394b07c30e24a54bdb8 Mon Sep 17 00:00:00 2001 From: Timothy Sanders Date: Tue, 17 Sep 2024 14:18:48 -0400 Subject: [PATCH 25/26] Update filename --- .github/ISSUE_TEMPLATE/{bug-fix-issue.md => bug-report-issue.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename .github/ISSUE_TEMPLATE/{bug-fix-issue.md => bug-report-issue.md} (100%) diff --git a/.github/ISSUE_TEMPLATE/bug-fix-issue.md b/.github/ISSUE_TEMPLATE/bug-report-issue.md similarity index 100% rename from .github/ISSUE_TEMPLATE/bug-fix-issue.md rename to .github/ISSUE_TEMPLATE/bug-report-issue.md From aba9344278abc3b2d36240af1429a9dbb15243c0 Mon Sep 17 00:00:00 2001 From: Timothy Sanders Date: Tue, 17 Sep 2024 14:25:28 -0400 Subject: [PATCH 26/26] Remove lines --- .github/ISSUE_TEMPLATE/bug-report-issue.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug-report-issue.md b/.github/ISSUE_TEMPLATE/bug-report-issue.md index 1da899d..1be5ec0 100644 --- a/.github/ISSUE_TEMPLATE/bug-report-issue.md +++ b/.github/ISSUE_TEMPLATE/bug-report-issue.md @@ -47,5 +47,4 @@ Please provide screenshots/screen capture or other evidence such as log files (s # Estimated Severity -If possible, provide an initial severity estimate of the issue. This of course can be adjusted after submission. - +If possible, provide an initial severity estimate of the issue. This of course can be adjusted after submission. \ No newline at end of file