doc: include updating release optional step

doc/contributing/releases.md

@@ -20,6 +20,7 @@ official release builds for Node.js, hosted on <https://nodejs.org/>.
   * [5. Create release commit](#5-create-release-commit)
   * [6. Propose release on GitHub](#6-propose-release-on-github)
   * [7. Ensure that the release branch is stable](#7-ensure-that-the-release-branch-is-stable)
+    * [7.1 Updating the release _(optional)_](#7-1-updating-the-release-optional)
   * [8. Produce a nightly build _(optional)_](#8-produce-a-nightly-build-optional)
   * [9. Produce release builds](#9-produce-release-builds)
   * [10. Test the build](#10-test-the-build)
@@ -545,6 +546,20 @@ with the Build Working Group.
 
 </details>
 
+#### 7.1 Updating the release _(optional)_
+
+Sometimes a release might be deferred to the subsequent day due to several conditions:
+
+* Unstable CI
+* Bad commit, requiring a git bisect and updating the proposal
+* Late CI completion
+
+And when it happens, the CHANGELOG_Vx and the commit metadata needs to be updated
+according to the new target date.
+
+However, if it's just the changelog/commit message that has changed since the last CI
+execution, there's no need to rerun CI, V8, or CITGM workflows.
+
 ### 8. Produce a nightly build _(optional)_
 
 If there is a reason to produce a test release for the purpose of having others