Skip to content

Commit

Permalink
Release Docs: Troubleshooting failed "Bump version" job (#42936)
Browse files Browse the repository at this point in the history
* Release Docs: Troubleshooting failed "Bump version" job

* Update docs/contributors/code/release.md

Co-authored-by: Dave Smith <getdavemail@gmail.com>
  • Loading branch information
Mamaduka and getdave authored Aug 4, 2022
1 parent 88899c8 commit b8e22a1
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions docs/contributors/code/release.md
Original file line number Diff line number Diff line change
Expand Up @@ -186,6 +186,10 @@ This is expected. The draft release will contain only the plugin zip. Only once
Yes. The method for this is identical to the main Plugin release process. You will need a Gutenberg Core team member to approve the release workflow.

> The release process failed to cherry-pick version bump commit to the trunk branch.
First, confirm that the step failed by checking the latest commits on `trunk` do not include the version bump commit. Then revert the version bump commit on the release branch - `git revert --no-edit {commitHash}`. Finally, push the changes and start the release process again.

## Packages Releases to npm and WordPress Core Updates

The Gutenberg repository follows the [WordPress SVN repository's](https://make.wordpress.org/core/handbook/about/release-cycle/) branching strategy for every major WordPress release. In addition to that, it also contains two other special branches that control npm publishing workflows:
Expand Down

0 comments on commit b8e22a1

Please sign in to comment.