From d47a2fdf8e2313a9a13e96dd32b8c5322a43cbdd Mon Sep 17 00:00:00 2001 From: Create or Update Pull Request Action Date: Mon, 15 Sep 2025 08:05:38 +0000 Subject: [PATCH 1/2] docs: update external docs --- _includes/readmes/body-parser.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/_includes/readmes/body-parser.md b/_includes/readmes/body-parser.md index 9fcd4c6f8e..7fe2e56935 100644 --- a/_includes/readmes/body-parser.md +++ b/_includes/readmes/body-parser.md @@ -76,6 +76,11 @@ object after the middleware (i.e. `req.body`). The `json` function takes an optional `options` object that may contain any of the following keys: +##### defaultCharset + +Specify the default character set for the json content if the charset is not +specified in the `Content-Type` header of the request. Defaults to `utf-8`. + ##### inflate When set to `true`, then deflated (compressed) bodies will be inflated; when @@ -291,7 +296,7 @@ Whether to decode numeric entities such as `☺` when parsing an iso-8859-1 form. Defaults to `false`. -#### depth +##### depth The `depth` option is used to configure the maximum depth of the `qs` library when `extended` is `true`. This allows you to limit the amount of keys that are parsed and can be useful to prevent certain types of abuse. Defaults to `32`. It is recommended to keep this value as low as possible. From cceb79fc7a183a2b7141dbe9ebfc5086e05d69b0 Mon Sep 17 00:00:00 2001 From: Create or Update Pull Request Action Date: Mon, 6 Oct 2025 08:05:29 +0000 Subject: [PATCH 2/2] docs: update external docs --- en/resources/contributing.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/en/resources/contributing.md b/en/resources/contributing.md index 4db6525dfe..4a385b3530 100644 --- a/en/resources/contributing.md +++ b/en/resources/contributing.md @@ -182,6 +182,26 @@ The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/doc The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains) +### Inactivity and Emeritus Policy for Any Role + +To support the health and continuity of the project, all individuals holding a role within the community (such as Triager, Committer, WG member, Project Captain, or TC member) are encouraged to maintain active participation. + +Inactivity is defined as the absence of meaningful involvement in the project—such as contributions, code reviews, triage, meeting attendance, or discussion participation—for a continuous period of 6 months. + +#### Exceptions + +Anyone may request a temporary leave from active participation due to personal or professional reasons. In such cases, the individual should inform the relevant team or the Technical Committee (TC). During this time, the inactivity policy is paused, and the individual will not be flagged as inactive. + +#### Inactivity Process + +* If someone is deemed inactive, the individual may be transitioned to an emeritus role that reflects their past contributions. A best effort will be made to inform them that this has occurred. They may request to be reinstated when they are ready to be active again. +* The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time. + +#### Accountability + +* The Technical Committee (TC) and the respective captains of each package/team are responsible for assessing activity levels and enacting this policy fairly and transparently, in coordination with other relevant teams. +* In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team. + ### Developer's Certificate of Origin 1.1 ```text