Answer: To pin a specific Kiro version, don't publish a versions[] entry higher than the release your fleet runs. For a phased rollout, govern rollout through the metadata your mirror serves; at or after rollout.start, kiro-cli update --rollout follows staged percentage selection while a plain kiro-cli update bypasses it. Status: Confirmed Entry: tool/kiro/admin-and-enterprise/pin-version-phased-rollout Revision: 1 Digest: sha256:8f5390ecc52a50d9 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:40:59Z Last changed: 2026-11-13T03:40:59Z Last verified: 2026-11-20T13:26:39Z Next check: 2026-11-21T13:26:39Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Pinning method | don't publish a versions[] entry higher than the release your fleet runs | [1] | 2026-11-20 Rollout control | govern rollout through the metadata your mirror serves | [1] | 2026-11-20 Staged selection flag | kiro-cli update --rollout | [1] | 2026-11-20 Rollout start | rollout.start | [1] | 2026-11-20 Windows override | --force | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Managed updates - Enterprise - Docs - Kiro". https://kiro.dev/docs/enterprise/managed-updates/ Role: primary. Accessed: 2026-11-20T13:26:39Z Quote: "To pin, don't publish a versions[] entry higher than the release your fleet runs." (Supports: Pinning method) Quote: "so you govern rollout through the metadata your mirror serves" (Supports: Rollout control) Quote: "a plain kiro-cli update bypasses staged percentage selection, while kiro-cli update --rollout follows it" (Supports: Staged selection flag) Quote: "Before rollout.start , Kiro CLI does not select the version." (Supports: Rollout start) Quote: "on Windows, --force can override this" (Supports: Windows override) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: b033d8e76b879ce8bff3bb21a1c295b68c1666cc432eca52ef19ea8ff69597d3 (captured 2026-11-20T13:26:38Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:26:39Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:26:39Z Last attempt: 2026-11-20T13:26:39Z Notes and limitations: Extracted automatically from a single official source (section "Pinning and staged rollout"). Related: https://latestn.com/tool/kiro/admin-and-enterprise/prepare-s3-bucket-for-csv-reports How do I prepare an Amazon S3 bucket for Kiro CSV reports? https://latestn.com/tool/kiro/admin-and-enterprise/prepare-s3-bucket-for-reports What S3 bucket permissions and setup does Kiro require before exporting CSV reports? https://latestn.com/tool/kiro/admin-and-enterprise/prompt-logging-prerequisites What are the prerequisites for enabling prompt logging in Kiro? https://latestn.com/tool/kiro/admin-and-enterprise/opentelemetry-kms-key-setup How do I create a KMS key to prepare credentials for OpenTelemetry in Kiro? https://latestn.com/tool/kiro/admin-and-enterprise/opentelemetry-kms-secret-setup What KMS key and Secrets Manager secret do I need to configure for Kiro OpenTelemetry export? https://latestn.com/tool/kiro/admin-and-enterprise/owner-lock-governance How do I enable the owner lock or configure governance policies like remote fleet policy in Kiro Crew? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:40:59Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/admin-and-enterprise/pin-version-phased-rollout/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/admin-and-enterprise/pin-version-phased-rollout POST: https://latestn.com/dispute/tool/kiro/admin-and-enterprise/pin-version-phased-rollout with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/admin-and-enterprise/pin-version-phased-rollout?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I pin a specific Kiro version or set up a phased rollout for managed updates? Revision 1, last verified 2026-11-20T13:26:39Z. https://latestn.com/tool/kiro/admin-and-enterprise/pin-version-phased-rollout (accessed 2026-11-21T10:06:58Z). @misc{LatestN_tool_kiro_admin_and_enterprise_pin_version_phased_rollout_r1, title = {How do I pin a specific Kiro version or set up a phased rollout for managed updates?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/admin-and-enterprise/pin-version-phased-rollout}}, note = {Revision 1; digest sha256:8f5390ecc52a50d9; last verified 2026-11-20T13:26:39Z; accessed 2026-11-21T10:06:58Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/admin-and-enterprise/pin-version-phased-rollout