From 0757628b62656f1505a1854c605276e3707dd371 Mon Sep 17 00:00:00 2001 From: Peter Sorensen <6152801+psorensen@users.noreply.github.com> Date: Fri, 9 Feb 2024 11:49:33 -0800 Subject: [PATCH] Update Releasing.md Fix typo --- _includes/markdown/Releasing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_includes/markdown/Releasing.md b/_includes/markdown/Releasing.md index 4ca1fd6..0e78562 100644 --- a/_includes/markdown/Releasing.md +++ b/_includes/markdown/Releasing.md @@ -41,7 +41,7 @@ In addition, ensure a ["Dependency Review" GitHub Action](https://github.com/10u

Release Process {% include Util/link_anchor anchor="release-process" %} {% include Util/top %}

-All releases should follow one of two [release processes we’ve crafted](https://github.com/10up/.github/blob/trunk/CONTRIBUTING.md#release-instructions) (i.e., when releasing a plugin to WordPress.org with [Ads.txt](https://github.com/10up/ads-txt/blob/develop/CONTRIBUTING.md#release-instructions) as an example, when not releasing a plugin to WordPress.org with [Distributor](https://github.com/10up/distributor/blob/develop/CONTRIBUTING.md#release-instructions)as an example) or even more simply, leverage a GitHub Action to automate the release and deploy to WordPress.org as necessary. If this is a major release, we should consider publishing an update post on 10up.com/blog, related social sites, and updating any related microsites. All WordPress plugin-related projects should utilize our [GitHub Action to deploy releases to WordPress.org](https://github.com/10up/action-wordpress-plugin-deploy) as well as our [GitHub Action to deploy readme and asset updates to WordPress.org](https://github.com/10up/action-wordpress-plugin-asset-update) (e.g., bumping the WordPress `Tested up to` value, updating screenshots). Both of these actions help automate the integration and management of WordPress.org's SVN-based repository, help eliminate human erros from working with SVN, and keep our released assets on WordPress.org a bit more secure (as access to SVN is gated by a bot account that the GitHub Action has access to via GitHub organization secrets). +All releases should follow one of two [release processes we’ve crafted](https://github.com/10up/.github/blob/trunk/CONTRIBUTING.md#release-instructions) (i.e., when releasing a plugin to WordPress.org with [Ads.txt](https://github.com/10up/ads-txt/blob/develop/CONTRIBUTING.md#release-instructions) as an example, when not releasing a plugin to WordPress.org with [Distributor](https://github.com/10up/distributor/blob/develop/CONTRIBUTING.md#release-instructions)as an example) or even more simply, leverage a GitHub Action to automate the release and deploy to WordPress.org as necessary. If this is a major release, we should consider publishing an update post on 10up.com/blog, related social sites, and updating any related microsites. All WordPress plugin-related projects should utilize our [GitHub Action to deploy releases to WordPress.org](https://github.com/10up/action-wordpress-plugin-deploy) as well as our [GitHub Action to deploy readme and asset updates to WordPress.org](https://github.com/10up/action-wordpress-plugin-asset-update) (e.g., bumping the WordPress `Tested up to` value, updating screenshots). Both of these actions help automate the integration and management of WordPress.org's SVN-based repository, help eliminate human errors from working with SVN, and keep our released assets on WordPress.org a bit more secure (as access to SVN is gated by a bot account that the GitHub Action has access to via GitHub organization secrets). Once a release has been tagged on GitHub, include the link to the release tag in the related milestone, ensure the milestone date is accurate, move any remaining open issues or PRs from the milestone to a future milestone, remove any closed but unmerged PRs from the milestone, and then close the milestone.