Skip to content

docs: clarify release authorization and permissions in release process #387

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
merged 5 commits into from
Sep 29, 2025
Merged

docs: clarify release authorization and permissions in release process #387

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
ca5758e
docs: clarify release authorization and permissions in release process
bjohansebas May 29, 2025
891cdf7
docs: enhance clarity and detail in release process documentation
bjohansebas Aug 8, 2025
a03d934
Revert "docs: enhance clarity and detail in release process documenta…
bjohansebas Aug 21, 2025
7cd0549
docs: simplify the changes
bjohansebas Aug 21, 2025
9f1bd9c
formmat
bjohansebas Aug 21, 2025
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
18 changes: 9 additions & 9 deletions docs/contributing/release-process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,25 +2,25 @@

This document contains the technical aspects of the Express release process. The
intended audience is those who have been authorized by the Express Technical
Committee (TC) to create, promote and sign official release builds for Express,
as npm packages hosted on <https://npmjs.com/package/express>.
Committee (TC) to create, promote and sign official release builds for any
package governed by Express.

## Who can make releases?

Release authorization is given by the Express TC. Once authorized, an individual
must have the following access permissions:
According to project governance, only package Captains or members of the Technical
Committee (TC) are permitted to make releases. Captains have the freedom to make releases
for their own package whenever necessary, while TC members may make releases for any package
as needed.

### 1. Github release access

The individual making the release will need to be a member of the
expressjs/express team with Write permission level so they are able to tag the
release commit and push changes to the expressjs/express repository
(see Steps 4 and 5).
The person making the release must be either the package captain or a member of the TC in
order to have sufficient permissions to do the work.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change is because it was referring only to Express and not in general


### 2. npmjs.com release access

The individual making the release will need to be made an owner on the
`express` package on npmjs.com so they are able to publish the release
package on npmjs.com so they are able to publish the release
(see Step 6).

## How to publish a release
Expand Down