# Release notes 0.1.174

> 30 October 2026: Customer review fixes for change approval, standard changes, compliance wording and number formatting.

_Release notes · Updated 2026-10-31 · Describes release 0.1.180_

## 0.1.174 — 30 October 2026 {#0-1-174-30-october-2026}

Customer review fixes for change approval, standard changes, compliance wording and number formatting. No new route; one new optional request field (`schedule_window: true`, `note`) on approve and release.

### Approve any time, run in the window {#approve-any-time-run-in-the-window}

- **A normal change can be approved while its maintenance window is closed.** The approval is recorded at once and the change is scheduled for the next window opening, where it runs; it never runs outside the window. The incident and change pages offer **Approve — runs in the next window (time)** instead of a disabled button. Emergency changes are unchanged.
- **Approval notes.** An approver can add a note when approving or releasing; it is kept with the approval in the change record and printed in the change request document.
- **Post-implementation review stays emergency-only.** Only an emergency change owed one before this release too; the change-control guide now says so. Normal and standard changes never open one.

### Standard changes run by the operator {#standard-changes-run-by-the-operator}

- **An operator runs a standard change raised from an incident in one click: Run standard change.** This applies when a certified runbook makes the incident's change standard at a one-approver tier: no approval request and no approver step. The change record and the change request document show a "Pre-approved standard change — runbook … certified by …" entry instead of an approval. A standard change at the two-approver tier (L3), one not raised from an incident, and one a runbook skill made standard on a P1 or critical incident still need their approvers, pending a decision on those cases. The page reads the standard lane from the server, so a change the server does not treat as standard keeps its normal approval.

### A compliance finding is called a finding {#a-compliance-finding-is-called-a-finding}

- **Records from cloud scanners and compliance checks read "finding"** everywhere: the pipeline steps, summary, dialogs, notices, timeline, chat, the change page, the change request document and notifications. Operational incidents keep "incident". Identifiers, e-mail addresses and external error text are shown as they are.

### Numbers {#numbers}

- **Totals, counts and money are grouped** (1,118,124; $1,234.56) on the portal pages, tables, the service-delivery report and its export, and the generated Markdown and DOCX documents. CSV and JSON exports are unchanged.


## Next steps

- Next: [Release notes 0.1.173](/help/release-notes-0-1-173.md)
- [All What's new pages](/help/what-s-new/llms.txt)
- [Documentation home](/help/)