docs: update API documentation

Author: rushbot

websites/api.rushstack.io/data/api_nav.json

@@ -4778,6 +4778,11 @@
               "label": "rushAlerts",
               "id": "pages/rush-lib.iexperimentsjson.rushalerts"
             },
+            {
+              "type": "doc",
+              "label": "strictChangefileValidation",
+              "id": "pages/rush-lib.iexperimentsjson.strictchangefilevalidation"
+            },
             {
               "type": "doc",
               "label": "useIPCScriptsInWatchMode",
@@ -6422,6 +6427,11 @@
               "label": "minimumReleaseAgeExclude",
               "id": "pages/rush-lib.pnpmoptionsconfiguration.minimumreleaseageexclude"
             },
+            {
+              "type": "doc",
+              "label": "minimumReleaseAgeMinutes",
+              "id": "pages/rush-lib.pnpmoptionsconfiguration.minimumreleaseageminutes"
+            },
             {
               "type": "doc",
               "label": "pnpmLockfilePolicies",

websites/api.rushstack.io/docs/pages/rush-lib.iexperimentsjson.md

@@ -290,6 +290,25 @@ boolean
 **_(BETA)_** _(Optional)_ (UNDER DEVELOPMENT) The Rush alerts feature provides a way to send announcements to engineers working in the monorepo, by printing directly in the user's shell window when they invoke Rush commands. This ensures that important notices will be seen by anyone doing active development, since people often ignore normal discussion group messages or don't know to subscribe.
 
 
+</td></tr>
+<tr><td>
+
+[strictChangefileValidation?](./rush-lib.iexperimentsjson.strictchangefilevalidation.md)
+
+
+</td><td>
+
+
+</td><td>
+
+boolean
+
+
+</td><td>
+
+**_(BETA)_** _(Optional)_ If true, `rush change --verify` will perform additional validation of change files. Specifically, it will report errors if change files reference projects that do not exist in the Rush configuration, or if change files target a project that belongs to a lockstepped version policy but is not the policy's main project.
+
+
 </td></tr>
 <tr><td>
 

websites/api.rushstack.io/docs/pages/rush-lib.iexperimentsjson.strictchangefilevalidation.md

@@ -0,0 +1,22 @@
+---
+hide_title: true
+custom_edit_url: null
+pagination_prev: null
+pagination_next: null
+---
+<!-- Do not edit this file. It is automatically generated by API Documenter. -->
+
+[Home](./index.md) &gt; [@microsoft/rush-lib](./rush-lib.md) &gt; [IExperimentsJson](./rush-lib.iexperimentsjson.md) &gt; [strictChangefileValidation](./rush-lib.iexperimentsjson.strictchangefilevalidation.md)
+
+## IExperimentsJson.strictChangefileValidation property
+
+> This API is provided as a beta preview for developers and may change based on feedback that we receive. Do not use this API in a production environment.
+> 
+
+If true, `rush change --verify` will perform additional validation of change files. Specifically, it will report errors if change files reference projects that do not exist in the Rush configuration, or if change files target a project that belongs to a lockstepped version policy but is not the policy's main project.
+
+**Signature:**
+
+```typescript
+strictChangefileValidation?: boolean;
+```

websites/api.rushstack.io/docs/pages/rush-lib.pnpmoptionsconfiguration.md

@@ -370,8 +370,6 @@ number \| undefined
 
 </td><td>
 
-The minimum number of minutes that must pass after a version is published before pnpm will install it. This setting helps reduce the risk of installing compromised packages, as malicious releases are typically discovered and removed within a short time frame.
-
 
 </td></tr>
 <tr><td>
@@ -391,7 +389,28 @@ string\[\] \| undefined
 
 </td><td>
 
-List of package names or patterns that are excluded from the minimumReleaseAge check. These packages will always install the newest version immediately, even if minimumReleaseAge is set.
+List of package names or patterns that are excluded from the minimumReleaseAge check. These packages will always install the newest version immediately, even if minimumReleaseAgeMinutes is set.
+
+
+</td></tr>
+<tr><td>
+
+[minimumReleaseAgeMinutes](./rush-lib.pnpmoptionsconfiguration.minimumreleaseageminutes.md)
+
+
+</td><td>
+
+`readonly`
+
+
+</td><td>
+
+number \| undefined
+
+
+</td><td>
+
+The minimum number of minutes that must pass after a version is published before pnpm will install it. This setting helps reduce the risk of installing compromised packages, as malicious releases are typically discovered and removed within a short time frame.
 
 
 </td></tr>

websites/api.rushstack.io/docs/pages/rush-lib.pnpmoptionsconfiguration.minimumreleaseage.md

@@ -10,19 +10,13 @@ pagination_next: null
 
 ## PnpmOptionsConfiguration.minimumReleaseAge property
 
-The minimum number of minutes that must pass after a version is published before pnpm will install it. This setting helps reduce the risk of installing compromised packages, as malicious releases are typically discovered and removed within a short time frame.
+> Warning: This API is now obsolete.
+> 
+> Use [PnpmOptionsConfiguration.minimumReleaseAgeMinutes](./rush-lib.pnpmoptionsconfiguration.minimumreleaseageminutes.md) instead.
+> 
 
 **Signature:**
 
 ```typescript
-readonly minimumReleaseAge: number | undefined;
+get minimumReleaseAge(): number | undefined;
 ```
-
-## Remarks
-
-(SUPPORTED ONLY IN PNPM 10.16.0 AND NEWER)
-
-PNPM documentation: https://pnpm.io/settings\#minimumreleaseage
-
-The default value is 0 (disabled).
-

websites/api.rushstack.io/docs/pages/rush-lib.pnpmoptionsconfiguration.minimumreleaseageexclude.md

@@ -10,7 +10,7 @@ pagination_next: null
 
 ## PnpmOptionsConfiguration.minimumReleaseAgeExclude property
 
-List of package names or patterns that are excluded from the minimumReleaseAge check. These packages will always install the newest version immediately, even if minimumReleaseAge is set.
+List of package names or patterns that are excluded from the minimumReleaseAge check. These packages will always install the newest version immediately, even if minimumReleaseAgeMinutes is set.
 
 **Signature:**
 

websites/api.rushstack.io/docs/pages/rush-lib.pnpmoptionsconfiguration.minimumreleaseageminutes.md

@@ -0,0 +1,28 @@
+---
+hide_title: true
+custom_edit_url: null
+pagination_prev: null
+pagination_next: null
+---
+<!-- Do not edit this file. It is automatically generated by API Documenter. -->
+
+[Home](./index.md) &gt; [@microsoft/rush-lib](./rush-lib.md) &gt; [PnpmOptionsConfiguration](./rush-lib.pnpmoptionsconfiguration.md) &gt; [minimumReleaseAgeMinutes](./rush-lib.pnpmoptionsconfiguration.minimumreleaseageminutes.md)
+
+## PnpmOptionsConfiguration.minimumReleaseAgeMinutes property
+
+The minimum number of minutes that must pass after a version is published before pnpm will install it. This setting helps reduce the risk of installing compromised packages, as malicious releases are typically discovered and removed within a short time frame.
+
+**Signature:**
+
+```typescript
+readonly minimumReleaseAgeMinutes: number | undefined;
+```
+
+## Remarks
+
+(SUPPORTED ONLY IN PNPM 10.16.0 AND NEWER)
+
+PNPM documentation: https://pnpm.io/settings\#minimumreleaseage
+
+The default value is 0 (disabled).
+