From b6669c6b11fbdc47db34334a8f82e043b8e2a501 Mon Sep 17 00:00:00 2001 From: thrijith Date: Fri, 19 Jul 2024 13:36:07 +0530 Subject: [PATCH 1/2] Add build zip --- .github/workflows/build-release-zip.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 .github/workflows/build-release-zip.yml diff --git a/.github/workflows/build-release-zip.yml b/.github/workflows/build-release-zip.yml new file mode 100644 index 0000000..ef21d9a --- /dev/null +++ b/.github/workflows/build-release-zip.yml @@ -0,0 +1,21 @@ +name: Build release zip + +on: + workflow_dispatch: + workflow_call: + push: + branches: + - trunk + - feature/add-zip-build + +jobs: + build: + name: Build release zip + runs-on: ubuntu-latest + + steps: + - name: Checkout + uses: actions/checkout@v4 + + - name: Generate ZIP file + uses: 10up/action-wordpress-plugin-build-zip@stable \ No newline at end of file From c5c0ce481fd978d8dacb6b8861e95552345adcc4 Mon Sep 17 00:00:00 2001 From: thrijith Date: Fri, 19 Jul 2024 14:24:15 +0530 Subject: [PATCH 2/2] Remove feature branch from release zip test Update CONTRIBUTING.md --- .github/workflows/build-release-zip.yml | 1 - CONTRIBUTING.md | 11 ++++++----- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/.github/workflows/build-release-zip.yml b/.github/workflows/build-release-zip.yml index ef21d9a..1754336 100644 --- a/.github/workflows/build-release-zip.yml +++ b/.github/workflows/build-release-zip.yml @@ -6,7 +6,6 @@ on: push: branches: - trunk - - feature/add-zip-build jobs: build: diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d8d38d9..6ed5c5c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -38,8 +38,9 @@ The `develop` branch is the development branch which means it contains the next 8. Test: While still on the `trunk` branch, test for functionality locally. 9. Push: Push your `trunk` branch to GitHub (e.g. `git push origin trunk`). 10. [Compare](https://github.com/10up/figma-block/compare/trunk...develop) trunk to develop to ensure no additional changes were missed. -11. Release: Create a [new release](https://github.com/10up/wp-newrelic/releases/new), naming the tag and the release with the new version number, and targeting the `trunk` branch. Paste the changelog from `CHANGELOG.md` into the body of the release and include a link to the closed issues on the [X.Y.Z milestone](https://github.com/10up/wp-newrelic/milestone/1?closed=1). -12. SVN: Wait for the [GitHub Action](https://github.com/10up/wp-newrelic/actions) to finish deploying to the WordPress.org repository. If all goes well, users with SVN commit access for that plugin will receive an emailed diff of changes. -13. Check WordPress.org: Ensure that the changes are live on https://wordpress.org/plugins/wp-newrelic/. This may take a few minutes. -14. Close milestone: Edit the [X.Y.Z milestone](https://github.com/10up/wp-newrelic/milestone/#) with release date (in the `Due date (optional)` field) and link to GitHub release (in the `Description` field), then close the milestone. -15. Punt incomplete items: If any open issues or PRs which were milestoned for `X.Y.Z` do not make it into the release, update their milestone to `X.Y.Z+1`, `X.Y+1.0`, `X+1.0.0` or `Future Release`. +11. Test the pre-release ZIP locally by downloading it from the Build release zip action artifact and installing it locally. Ensure this zip has all the files we expect, that it installs and activates correctly and that all basic functionality is working. +12. Release: Create a [new release](https://github.com/10up/wp-newrelic/releases/new), naming the tag and the release with the new version number, and targeting the `trunk` branch. Paste the changelog from `CHANGELOG.md` into the body of the release and include a link to the closed issues on the [X.Y.Z milestone](https://github.com/10up/wp-newrelic/milestone/1?closed=1). +13. SVN: Wait for the [GitHub Action](https://github.com/10up/wp-newrelic/actions) to finish deploying to the WordPress.org repository. If all goes well, users with SVN commit access for that plugin will receive an emailed diff of changes. +14. Check WordPress.org: Ensure that the changes are live on https://wordpress.org/plugins/wp-newrelic/. This may take a few minutes. +15. Close milestone: Edit the [X.Y.Z milestone](https://github.com/10up/wp-newrelic/milestone/#) with release date (in the `Due date (optional)` field) and link to GitHub release (in the `Description` field), then close the milestone. +16. Punt incomplete items: If any open issues or PRs which were milestoned for `X.Y.Z` do not make it into the release, update their milestone to `X.Y.Z+1`, `X.Y+1.0`, `X+1.0.0` or `Future Release`.