Skip to content

Commit 09c68ee

Browse files
committed
doc: include updating release optional step
1 parent a03529d commit 09c68ee

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

doc/contributing/releases.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,7 @@ official release builds for Node.js, hosted on <https://nodejs.org/>.
2020
* [5. Create release commit](#5-create-release-commit)
2121
* [6. Propose release on GitHub](#6-propose-release-on-github)
2222
* [7. Ensure that the release branch is stable](#7-ensure-that-the-release-branch-is-stable)
23+
* [7.1 Updating the release _(optional)_](#7-1-updating-the-release-optional)
2324
* [8. Produce a nightly build _(optional)_](#8-produce-a-nightly-build-optional)
2425
* [9. Produce release builds](#9-produce-release-builds)
2526
* [10. Test the build](#10-test-the-build)
@@ -545,6 +546,24 @@ with the Build Working Group.
545546

546547
</details>
547548

549+
#### 7.1 Updating the release _(optional)_
550+
551+
Sometimes a release might be deferred to the subsequent day due to several
552+
conditions:
553+
554+
* Unstable CI
555+
* Bad commit, requiring a git bisect and updating the proposal
556+
* Late CI completion
557+
558+
And when it happens, the CHANGELOG\_Vx and the commit metadata needs to be
559+
updated according to the new target date.
560+
561+
However, if it's just the changelog/commit message that has changed since the
562+
last CI execution, there's no need to rerun CI, V8, or CITGM workflows.
563+
564+
The PR still needs a clean GitHub action run, and the original CI, V8, and
565+
CITGM run should be in a visible comment.
566+
548567
### 8. Produce a nightly build _(optional)_
549568

550569
If there is a reason to produce a test release for the purpose of having others

0 commit comments

Comments
 (0)