Merge branch 'develop' into stable

.github/release-pull-request-template.md

@@ -5,7 +5,7 @@
 - [ ] Merge: Make a non-fast-forward merge from your release branch to `develop` (or merge the pull request), then merge `develop` into `stable` (`git checkout stable && git merge --no-ff develop`).
 - [ ] Push: Push your stable branch to GitHub (e.g. `git push origin stable`).
 - [ ] Release: Create a [new release](https://github.com/10up/action-wordpress-plugin-build-zip/releases/new), naming the tag and the release with the new version number, and targeting the `stable` branch. Paste the changelog from `CHANGELOG.md` into the body of the release and include a link to the closed issues on the [milestone](https://github.com/10up/action-wordpress-plugin-build-zip/milestones/#?closed=1).  The release should now appear under [releases](https://github.com/10up/action-wordpress-plugin-build-zip/releases).
-- [ ] Ensure the release [appears in the GitHub Marketplace](https://github.com/marketplace/actions/wordpress-plugin-build-release) correctly.
-- [ ] Close milestone: Edit the [milestone](https://github.com/10up/action-wordpress-plugin-build-release/milestones/) with release date (in the `Due date (optional)` field) and link to GitHub release (in the `Description field`), then close the milestone.
+- [ ] Ensure the release [appears in the GitHub Marketplace](https://github.com/marketplace/actions/wordpress-plugin-build-zip) correctly.
+- [ ] Close milestone: Edit the [milestone](https://github.com/10up/action-wordpress-plugin-build-zip/milestones/) with release date (in the `Due date (optional)` field) and link to GitHub release (in the `Description field`), then close the milestone.
 - [ ] 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+- [ ]0`, `X+- [ ]0.0` or `Future Release`.
 - [ ] Celebrate shipping!

.github/workflows/no-response.yml → .github/workflows/close-stale-issues.yml

@@ -1,30 +1,36 @@
-name: No Response
+name: 'Close stale issues'
 
 # **What it does**: Closes issues where the original author doesn't respond to a request for information.
 # **Why we have it**: To remove the need for maintainers to remember to check back on issues periodically to see if contributors have responded.
-# **Who does it impact**: Everyone that works on docs or docs-internal.
 
 on:
-  issue_comment:
-    types: [created]
   schedule:
-    # Schedule for five minutes after the hour, every hour
-    - cron: '5 * * * *'
+    # Schedule for every day at 1:30am UTC
+    - cron: '30 1 * * *'
+
+permissions:
+  issues: write
 
 jobs:
-  noResponse:
+  stale:
     runs-on: ubuntu-latest
     steps:
-      - uses: lee-dohm/no-response@v0.5.0
+      - uses: actions/stale@v9
         with:
-          token: ${{ github.token }}
-          daysUntilClose: 14 # Number of days of inactivity before an Issue is closed for lack of response
-          responseRequiredLabel: "needs:feedback" # Label indicating that a response from the original author is required
-          closeComment: >
+          days-before-stale: 7
+          days-before-close: 7
+          stale-issue-message: >
+            It has been 7 days since more information was requested from you in this issue and we have not heard back. This issue is now marked as stale and will be closed in 7 days, but if you have more information to add then please comment and the issue will stay open.
+          close-issue-message: >
             This issue has been automatically closed because there has been no response
             to our request for more information. With only the
             information that is currently in the issue, we don't have enough information
             to take action. Please reach out if you have or find the answers we need so
             that we can investigate further. See [this blog post on bug reports and the
             importance of repro steps](https://www.lee-dohm.com/2015/01/04/writing-good-bug-reports/)
             for more information about the kind of information that may be helpful.
+          stale-issue-label: 'stale'
+          close-issue-reason: 'not_planned'
+          any-of-labels: 'needs:feedback'
+          remove-stale-when-updated: true
+

CHANGELOG.md

@@ -4,9 +4,13 @@ All notable changes to this project will be documented in this file, per [the Ke
 
 ## [Unreleased] - TBD
 
-## [1.0.0] - 2022-12-01
+## [1.0.1] - 2024-03-20
+### Changed
+- Updated to v4 of `upload-artifact`, the action now exposes the artifact URL with: `${{ steps.upload-plugin-artifact.outputs.artifact-url }}` (props [@jdevalk](https://github.com/jdevalk) via [#3](https://github.com/10up/action-wordpress-plugin-build-zip/pull/3)).
 
+## [1.0.0] - 2022-12-01
 - Initial release.
 
 [Unreleased]: https://github.com/10up/action-wordpress-plugin-build-zip/compare/stable...develop
+[1.0.1]: https://github.com/10up/action-wordpress-plugin-build-zip/compare/1.0.0...1.0.1
 [1.0.0]: https://github.com/10up/action-wordpress-plugin-build-zip/releases/tag/1.0.0

CREDITS.md

@@ -10,7 +10,7 @@ The following individuals are responsible for curating the list of issues, respo
 
 Thank you to all the people who have already contributed to this repository via bug reports, code, design, ideas, project management, translation, testing, etc.
 
-[Darin Kotter (@dkotter)](https://github.com/dkotter), [Jeffrey Paul (@jeffpaul)](https://github.com/jeffpaul).
+[Darin Kotter (@dkotter)](https://github.com/dkotter), [Jeffrey Paul (@jeffpaul)](https://github.com/jeffpaul), [Joost de Valk (@jdevalk)](https://github.com/jdevalk).
 
 ## Libraries
 

action.yml

@@ -22,8 +22,8 @@ runs:
       shell: bash
 
     - name: Upload the archive as an artifact
-      id: upload
-      uses: actions/upload-artifact@v3
+      id: upload-plugin-artifact
+      uses: actions/upload-artifact@v4
       with:
         name: ${{ github.event.repository.name }}
         path: zipfile