Skip to content

Commit 391167e

Browse files
authored
chore(docs): Update release PR links to match release-please label (#3457)
1 parent 66050d6 commit 391167e

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

docs/releasing/releasing.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Combined with our "squash and merge" preference on Pull Requests, each merged Pu
2424

2525
### [release-please](https://github.com/googleapis/release-please)
2626

27-
Create and manage [release PRs](https://github.com/trussworks/react-uswds/issues?q=is%3Apr%20author%3Aapp%2Fgithub-actions%20label%3A%22type%3A%20release%22) when releasable changes have been merged to `main`, based on our [release-please configuration](https://github.com/trussworks/react-uswds/blob/main/release-please-config.json).
27+
Create and manage [release PRs](https://github.com/trussworks/react-uswds/issues?q=is%3Apr%20is%3Aopen%20author%3Aapp%2Fgithub-actions%20label%3A%22autorelease%3A%20pending%22) when releasable changes have been merged to `main`, based on our [release-please configuration](https://github.com/trussworks/react-uswds/blob/main/release-please-config.json).
2828

2929
The primary purpose of release PRs is to update the [changelog](https://github.com/trussworks/react-uswds/blob/main/CHANGELOG.md) and increment the version number in [package.json](https://github.com/trussworks/react-uswds/blob/main/package.json).
3030

@@ -59,7 +59,7 @@ Additionally, at least one releasable change must have been merged to main since
5959

6060
Follow these steps to create and publish a release for a given version, `<major.minor.incremental>`.
6161

62-
1. Review and merge the current [release PR](https://github.com/trussworks/react-uswds/issues?q=is%3Apr%20author%3Aapp%2Fgithub-actions%20label%3A%22type%3A%20release%22).
62+
1. Review and merge the current [release PR](https://github.com/trussworks/react-uswds/issues?q=is%3Apr%20is%3Aopen%20author%3Aapp%2Fgithub-actions%20label%3A%22autorelease%3A%20pending%22).
6363
- Ensure the branch is up to date with `main`.
6464
- PR CI checks will likely be stuck in a pending state on the release PR requiring administrator override to merge. This is because GitHub actions in a workflow run cannot trigger new workflow runs. Since `release-please` creates and updates the release PR via a workflow action, PR checks will not run under normal circumstances. We consider this acceptable since release PRs do not change code.
6565
2. Wait for `release-please` to create the corresponding [tag](https://github.com/trussworks/react-uswds/tags) in GitHub including the updates from the changelog.

0 commit comments

Comments
 (0)