add 1.19

Author: kpcraig

content/vault/global/partials/important-changes/summary-tables/1_19.mdx

@@ -23,6 +23,7 @@ Introduced | Recommendations | Edition    | Change
 1.19.0     | No              | All        | [Transit support for Ed25519ph and Ed25519ctx signatures](/vault/docs/v1.19.x/updates/important-changes#ed25519)
 1.19.1     | **Yes**         | All        | [Strict validation for Azure auth login requests](/vault/docs/v1.19.x/updates/important-changes#strict-azure)
 1.19.9     | No              | All        | [JSON Payload Limits](/vault/docs/v1.19.x/updates/important-changes#json-limits)
+1.19.11    | **Yes**         | Enterprise | [Rotation manager schedule strings in UTC](/vault/docs/v1.19.x/updates/important-changes#rotation-manager-utc)
 
 
 ### Known issues

content/vault/v1.19.x/content/docs/updates/important-changes.mdx

@@ -160,6 +160,17 @@ If you use `file` audit devices, you need to:
 1. Use non-executable file modes (e.g., 0644, 0666) for log files.
 
 
+### Rotation manager schedule strings in UTC ((#rotation-manager-utc))
+
+| Change       | Affected version | Vault edition
+| ------------ | ---------------- | -------------
+| New behavior | 1.19.11+         | Enterprise
+
+Vault interprets `rotation_schedule` strings relative to UTC to match the
+behavior of static role rotations in the database plugin. Old rotations use
+their existing schedule until you manually update rotation with an API call.
+
+
 ## Breaking changes
 
 @include '../../../global/partials/important-changes/breaking-changes/cve-2025-6000.mdx'

content/vault/v1.19.x/content/partials/rotationfields.mdx

@@ -8,7 +8,8 @@
   defining the schedule on which Vault should rotate the root token. Standard
   cron-style time format uses five fields to define the minute, hour, day of
   month, month, and day of week respectively. For example, `0 0 * * SAT` tells
-  Vault to rotate the root token every Saturday at 00:00. **You must set one of
+  Vault to rotate the root token every Saturday at 00:00. In 1.19.11 or later,
+  Vault interprets the schedule in UTC. **You must set one of
   `rotation_schedule` or `rotation_period`, but cannot set both**.
 - `rotation_window` `(string/integer: 0)` – <EnterpriseAlert product="vault" inline />
   The maximum amount of time, in seconds, allowed to complete

content/vault/v1.20.x/content/partials/rotationfields.mdx

@@ -8,7 +8,7 @@
   defining the schedule on which Vault should rotate the root token. Standard
   cron-style time format uses five fields to define the minute, hour, day of
   month, month, and day of week respectively. For example, `0 0 * * SAT` tells
-  Vault to rotate the root token every Saturday at 00:00. Vault interprets the schedule in UTC.
+  Vault to rotate the root token every Saturday at 00:00. In 1.20.5 or later, Vault interprets the schedule in UTC.
   **You must set one of `rotation_schedule` or `rotation_period`, but cannot set both**.
 - `rotation_window` `(string/integer: 0)` – <EnterpriseAlert product="vault" inline />
   The maximum amount of time, in seconds, allowed to complete