@@ -20,6 +20,7 @@ official release builds for Node.js, hosted on <https://nodejs.org/>.
20
20
* [ 5. Create release commit] ( #5-create-release-commit )
21
21
* [ 6. Propose release on GitHub] ( #6-propose-release-on-github )
22
22
* [ 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 )
23
24
* [ 8. Produce a nightly build _ (optional)_ ] ( #8-produce-a-nightly-build-optional )
24
25
* [ 9. Produce release builds] ( #9-produce-release-builds )
25
26
* [ 10. Test the build] ( #10-test-the-build )
@@ -545,6 +546,24 @@ with the Build Working Group.
545
546
546
547
</details >
547
548
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
+
548
567
### 8. Produce a nightly build _ (optional)_
549
568
550
569
If there is a reason to produce a test release for the purpose of having others
0 commit comments