Skip to content

doc: add FAQ to releases section #55992

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nodejs-github-bot merged 2 commits into from
Nov 27, 2024
Merged

doc: add FAQ to releases section #55992

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
10f694e
doc: add FAQ to releases section
RafaelGSS Nov 25, 2024
0bb2fc4
Apply suggestions from code review
RafaelGSS Nov 26, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Apply suggestions from code review 
Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
  • Loading branch information
@RafaelGSS @aduh95
RafaelGSS and aduh95 authored Nov 26, 2024
commit 0bb2fc4cc5794dabbc772d213d193fcd813bea51
4 changes: 2 additions & 2 deletions doc/contributing/releases.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1385,7 +1385,7 @@ take place once a new LTS line has been released.

## FAQ

Due to how releases work (tools/release.sh) isn't uncommon to face some errors
Due to how `tools/release.sh` work, it isn't uncommon to face some errors
during the promotion process as it depends on network communication and machine
availability. This section aims to guide the releaser through potential
failures.
Expand Down Expand Up @@ -1413,7 +1413,7 @@ Emitted 'error' event on DestroyableTransform instance at:
}
```

Typical approach: Sign the release again
Typical resolution: sign the release again.

```bash
./tools/release.sh -s vX.Y.Z
Expand Down