Skip to content

OpenAI's Codex Security CLI and TypeScript SDK for finding, validating, and fixing security vulnerabilities. npm: https://www.npmjs.com/package/@openai/codex-security

fix(release): improve release note structure and formatting (#1804)

Michael D'Angelo2078aee07de5
diff --git a/.github/release-notes.md b/.github/release-notes.md
index 668e3f4a9..bc7954e0c 100644
--- a/.github/release-notes.md
+++ b/.github/release-notes.md
@@ -4,87 +4,12 @@
## Highlights
-Codex Security 0.5.0 adds investigation time budgets, host-provided finding
-reviews, and more inference provider options. It also improves saved finding
-evidence, usage reporting, and recovery after interrupted scans and publication.
-The minor version marks the retirement of advisory capability preflight;
-custom integrations should follow the migration guidance below.
-
-- Set an investigation allowance with `codex-security scan . --max-time 15`,
- SDK `maxTimeMinutes`, or project setting `scan.max_time_minutes`. Values are
- positive minutes, including fractions. Standard and diff scans treat the
- allowance as advisory; Deep Scan enforces it for discovery, then combines
- completed findings. Reporting can continue beyond the deadline. See the
- [time-budget guide](https://github.com/openai/codex-security/blob/npm-v0.5.0/sdk/typescript/docs/cli.md#set-investigation-time).
- ([#1674](https://github.com/openai/codex-security/pull/1674))
-- Hosts can validate findings against source with `codex-security validate --records`
- and `validateRecords()`, or classify canonical reports against a supplied
- severity rubric with `codex-security classify-severity --records` and
- `classifySeverityRecords()`. Both use host-provided model execution;
- classification requires no repository or saved scan. See the
- [validation guide](https://github.com/openai/codex-security/blob/npm-v0.5.0/sdk/typescript/docs/validate-records.md)
- and [classification guide](https://github.com/openai/codex-security/blob/npm-v0.5.0/sdk/typescript/docs/classify-severity-records.md)
- for input contracts and host responsibilities.
- ([#1682](https://github.com/openai/codex-security/pull/1682),
- [#1662](https://github.com/openai/codex-security/pull/1662))
-- Scans support Cheaper Inference through `--provider cheaperinference`, an
- explicit model, and `CHEAPER_INFERENCE_API_KEY`. The GitHub Action adds a
- `provider` input for Amazon Bedrock, OpenRouter, and Fireworks alongside the
- default OpenAI provider; non-OpenAI providers require an explicit model and
- the selected provider's credentials. See the
- [CLI provider documentation](https://github.com/openai/codex-security/blob/npm-v0.5.0/sdk/typescript/docs/cli.md)
- and [Action setup guide](https://github.com/openai/codex-security/blob/npm-v0.5.0/github-action/README.md#inference-providers).
- ([#1623](https://github.com/openai/codex-security/pull/1623),
- [#1677](https://github.com/openai/codex-security/pull/1677))
-- Hosted scans pass `reasoningEffort` strings through to the executor, including
- `max` and future values supported by the selected model or provider. The
- GitHub Action's `effort` input also accepts provider-supported strings and
- retains its `xhigh` default. Deep Scan forwards resolved native settings to
- fresh and resumed workers while retaining worker-specific permissions.
- ([#1712](https://github.com/openai/codex-security/pull/1712),
- [#1717](https://github.com/openai/codex-security/pull/1717))
-- Standard and diff scans use available workers and continue review in the
- parent when delegation is unavailable. Optional worker or goal-tool
- availability no longer depends on the removed capability registry.
- ([#1609](https://github.com/openai/codex-security/pull/1609))
-- Patching and fix verification use complete sealed findings from saved scans,
- preserving current triage and remediation state. Workbench excerpts stay
- tied to the source and scope of the saved scan, and publishing older findings
- preserves their historical root-cause details and code evidence.
- ([#1608](https://github.com/openai/codex-security/pull/1608),
- [#488](https://github.com/openai/codex-security/pull/488),
- [#1756](https://github.com/openai/codex-security/pull/1756))
-- Usage reporting distinguishes recorded tokens from missing worker receipts
- or unfinished turns. Partial totals display as "at least X tokens; some usage
- unavailable." Saved scan history includes parent/worker totals and
- measurement times alongside cost estimates; historical account-limit readings
- are not a live allowance check. See
- [progress and cost](https://github.com/openai/codex-security/blob/npm-v0.5.0/sdk/typescript/docs/cli.md#progress-and-cost).
- ([#1640](https://github.com/openai/codex-security/pull/1640))
-- Bulk-scan recovery validates completed artifacts before reusing them and
- preserves interrupted receipt bytes. Parallel workers serialize receipt
- writes, and publication replaces its latest receipt atomically. Completed
- Linear publication results remain available after late cancellation during
- a failed final receipt write.
- ([#1720](https://github.com/openai/codex-security/pull/1720),
- [#1748](https://github.com/openai/codex-security/pull/1748),
- [#1735](https://github.com/openai/codex-security/pull/1735),
- [#1738](https://github.com/openai/codex-security/pull/1738),
- [#1725](https://github.com/openai/codex-security/pull/1725))
-- Matching GitHub Action distributions publish their manifest, SBOM, and full
- distribution commit SHA in a companion `action-vX.Y.Z` release. Artifact
- upload failures propagate the original stream error and cancel active streams.
- ([#1711](https://github.com/openai/codex-security/pull/1711),
- [#1671](https://github.com/openai/codex-security/pull/1671))
-- Failed or canceled `dedupe --json --full-output` commands no longer print a
- false success envelope. Diff scans handle root commits in SHA-256
- repositories and read blobs with Git versions older than 2.38.
- ([#1071](https://github.com/openai/codex-security/pull/1071),
- [#1716](https://github.com/openai/codex-security/pull/1716),
- [#1715](https://github.com/openai/codex-security/pull/1715))
-- DOCX knowledge-base extraction excludes deleted revisions and field
- instructions while preserving visible field results.
- ([#1714](https://github.com/openai/codex-security/pull/1714))
+Codex Security 0.5.0 adds investigation time budgets, host-provided finding reviews, and more inference provider options. It also improves saved finding evidence, usage reporting, and recovery after interrupted scans and publication. The minor version marks the retirement of advisory capability preflight; custom integrations should follow the migration guidance below.
+
+- **Investigation budgets.** Set an investigation allowance with `codex-security scan . --max-time 15`, SDK `maxTimeMinutes`, or project setting `scan.max_time_minutes`. Values are positive minutes, including fractions. Standard and diff scans treat the allowance as advisory; Deep Scan enforces it for discovery, then combines completed findings. Reporting can continue beyond the deadline. See the [time-budget guide](https://github.com/openai/codex-security/blob/npm-v0.5.0/sdk/typescript/docs/cli.md#set-investigation-time). ([#1674](https://github.com/openai/codex-security/pull/1674))
+- **Host-provided finding reviews.** Hosts can validate findings against source with `codex-security validate --records` and `validateRecords()`, or classify canonical reports against a supplied severity rubric with `codex-security classify-severity --records` and `classifySeverityRecords()`. Both use host-provided model execution; classification requires no repository or saved scan. See the [validation guide](https://github.com/openai/codex-security/blob/npm-v0.5.0/sdk/typescript/docs/validate-records.md) and [classification guide](https://github.com/openai/codex-security/blob/npm-v0.5.0/sdk/typescript/docs/classify-severity-records.md) for input contracts and host responsibilities. ([#1682](https://github.com/openai/codex-security/pull/1682), [#1662](https://github.com/openai/codex-security/pull/1662))
+- **Inference providers.** Scans support Cheaper Inference through `--provider cheaperinference`, an explicit model, and `CHEAPER_INFERENCE_API_KEY`. The GitHub Action adds a `provider` input for Amazon Bedrock, OpenRouter, and Fireworks alongside the default OpenAI provider; non-OpenAI providers require an explicit model and the selected provider's credentials. See the [CLI provider documentation](https://github.com/openai/codex-security/blob/npm-v0.5.0/sdk/typescript/docs/cli.md) and [Action setup guide](https://github.com/openai/codex-security/blob/npm-v0.5.0/github-action/README.md#inference-providers). ([#1623](https://github.com/openai/codex-security/pull/1623), [#1677](https://github.com/openai/codex-security/pull/1677))
+- **Saved results and recovery.** Patching and fix verification use complete sealed evidence, and bulk scans validate saved artifacts before reusing completed results. See the upgrade guidance below.
<!-- release-section: highlights:end -->
@@ -92,10 +17,24 @@ custom integrations should follow the migration guidance below.
## Upgrade notes
+### Custom capability-preflight integrations
+
+The plugin's `scripts/config_preflight.py` helper and `preflight/capability-profiles.toml` registry are removed. Custom capability registries and helper-derived progress inputs and events are no longer supported.
+
+<details>
+<summary>Migration steps for custom integrations</summary>
+
+1. Remove helper invocations, custom-registry arguments, and gates that wait for a helper `ready` result. Replace references to `config-preflight.md` and `desktop-config-preflight.md` with the [scan runtime guidance](https://github.com/openai/codex-security/blob/npm-v0.5.0/plugins/codex-security/references/scan-runtime.md). Use available delegation tools and successful spawn results; continue in the parent when workers cannot start. Do not edit persistent configuration to enable optional workers or goal tools.
+2. Remove `kind: "preflight"` handling from `onWorkerStatus` consumers, including reads of `delegation` and `configuredSlots`, and stop waiting for the CLI's `worker.preflight` diagnostic. `onWorkerStatus` still emits `kind: "dispatch"` with `phase`, `planned`, and `started`. These counts are best-effort model reports; a missing event does not prove no worker ran.
+3. Stop sending `preflightChecks` to `update_codex_security_scan_progress` and remove the workbench arguments `--preflight-issues-json` and `--preflight-issues-json-stdin`. For host-backed Standard and diff scans, use the authoritative scan context and advance to `threat_model` before architecture mapping. Deep Scan's coordinator continues to own its setup and progress.
+
+</details>
+
+Saved preflight history remains readable, and the scan lifecycle still includes a `preflight` phase. Local SDK `preflight()` input checks, authentication, sandbox enforcement, and Deep worker configuration remain in effect. Normal CLI and SDK scans need no capability-preflight configuration migration. ([#1609](https://github.com/openai/codex-security/pull/1609))
+
### Investigation time settings
-Prefer the new minute-based settings for Standard, diff, and Deep scans. For
-existing Deep Scan configurations, convert hours to minutes:
+Prefer the new minute-based settings for Standard, diff, and Deep scans. For existing Deep Scan configurations, convert hours to minutes:
| Previous setting | Preferred setting |
| ------------------------------------- | ------------------------------------ |
@@ -103,79 +42,34 @@ existing Deep Scan configurations, convert hours to minutes:
| SDK `maxTimeHours: 2` | SDK `maxTimeMinutes: 120` |
| Project `scan.deep.max_time_hours: 2` | Project `scan.max_time_minutes: 120` |
-The hour-based settings, including legacy TOML `deep_scan.max_time_hours`, remain
-accepted as deprecated Deep-only aliases. Explicit settings override
-lower-priority configuration across units. At the winning configuration source,
-equivalent durations are accepted; conflicting minute/hour values are errors.
+The hour-based settings, including legacy TOML `deep_scan.max_time_hours`, remain accepted as deprecated Deep-only aliases. Explicit settings override lower-priority configuration across units. At the winning configuration source, equivalent durations are accepted; conflicting minute/hour values are errors.
-Standard scans still have no time allowance by default. An allowance is neither
-a hard timeout nor a minimum runtime. Deep Scan's default and maximum discovery
-duration remain 5760 minutes (96 hours). Resuming Deep Scan retains its original
-deadline; rerunning starts a new allowance. For batch and component scans,
-project time settings apply separately to each scan attempt, not the campaign
-as a whole. See the
-[time-budget guide](https://github.com/openai/codex-security/blob/npm-v0.5.0/sdk/typescript/docs/cli.md#set-investigation-time).
-([#1674](https://github.com/openai/codex-security/pull/1674))
+Standard scans still have no time allowance by default. An allowance is neither a hard timeout nor a minimum runtime. Deep Scan's default and maximum discovery duration remain 5760 minutes (96 hours). Resuming Deep Scan retains its original deadline; rerunning starts a new allowance. For batch and component scans, project time settings apply separately to each scan attempt, not the campaign as a whole. See the [time-budget guide](https://github.com/openai/codex-security/blob/npm-v0.5.0/sdk/typescript/docs/cli.md#set-investigation-time). ([#1674](https://github.com/openai/codex-security/pull/1674))
### Saved scan evidence and recovery
-Keep the complete sealed artifacts with saved scans used for patching or fix
-verification. Missing or mismatched evidence now stops those tasks instead of
-passing a shortened preview to the model. Bulk-scan resume validates saved
-contracts and seals before reusing a completed result; invalid or unsuccessful
-results start a new attempt while preserving the old artifacts.
-([#1608](https://github.com/openai/codex-security/pull/1608),
-[#1720](https://github.com/openai/codex-security/pull/1720))
+Keep the complete sealed artifacts with saved scans used for patching or fix verification. Missing or mismatched evidence now stops those tasks instead of passing a shortened preview to the model. Bulk-scan resume validates saved contracts and seals before reusing a completed result; invalid or unsuccessful results start a new attempt while preserving the old artifacts. ([#1608](https://github.com/openai/codex-security/pull/1608), [#1720](https://github.com/openai/codex-security/pull/1720))
### GitHub Action release assets
-If automation downloads the Action manifest or SBOM from an `npm-vX.Y.Z`
-release, switch those downloads to the matching `action-vX.Y.Z` release. The npm
-release remains the canonical changelog and Latest release; Action version tags
-and workflow usage syntax are unchanged. See the
-[Action release documentation](https://github.com/openai/codex-security/blob/npm-v0.5.0/github-action/README.md#development).
-([#1711](https://github.com/openai/codex-security/pull/1711))
-
-### Custom capability-preflight integrations
-
-The plugin's `scripts/config_preflight.py` helper and
-`preflight/capability-profiles.toml` registry are removed. Custom capability
-registries and helper-derived progress inputs and events are no longer supported.
-Update integrations as follows:
-
-1. Remove helper invocations, custom-registry arguments, and gates that wait for
- a helper `ready` result. Replace references to `config-preflight.md` and
- `desktop-config-preflight.md` with the
- [scan runtime guidance](https://github.com/openai/codex-security/blob/npm-v0.5.0/plugins/codex-security/references/scan-runtime.md).
- Use available delegation tools and successful spawn results; continue in the
- parent when workers cannot start. Do not edit persistent configuration to
- enable optional workers or goal tools.
-2. Remove `kind: "preflight"` handling from `onWorkerStatus` consumers,
- including reads of `delegation` and `configuredSlots`, and stop waiting for
- the CLI's `worker.preflight` diagnostic. `onWorkerStatus` still emits
- `kind: "dispatch"` with `phase`, `planned`, and `started`. These counts are
- best-effort model reports; a missing event does not prove no worker ran.
-3. Stop sending `preflightChecks` to
- `update_codex_security_scan_progress` and remove the workbench arguments
- `--preflight-issues-json` and `--preflight-issues-json-stdin`. For host-backed
- Standard and diff scans, use the authoritative scan context and advance to
- `threat_model` before architecture mapping. Deep Scan's coordinator continues
- to own its setup and progress.
-
-Saved preflight history remains readable, and the scan lifecycle still includes
-a `preflight` phase. Local SDK `preflight()` input checks, authentication,
-sandbox enforcement, and Deep worker configuration remain in effect. Normal
-CLI and SDK scans need no capability-preflight configuration migration.
-([#1609](https://github.com/openai/codex-security/pull/1609))
+If automation downloads the Action manifest or SBOM from an `npm-vX.Y.Z` release, switch those downloads to the matching `action-vX.Y.Z` release. The npm release remains the canonical changelog and Latest release; Action version tags and workflow usage syntax are unchanged. See the [Action release documentation](https://github.com/openai/codex-security/blob/npm-v0.5.0/github-action/README.md#development). ([#1711](https://github.com/openai/codex-security/pull/1711))
### Selected-profile approval policy
-An explicitly selected Codex profile's `approval_policy` now takes precedence
-over the root policy. If you previously relied on a root `never` policy despite
-a selected profile specifying `on-request`, set the selected profile's policy
-to `never` to continue denying permission requests. An absent or null profile
-policy still inherits the root value; Deep Scan workers retain their explicit
-`never` policy.
-([#530](https://github.com/openai/codex-security/pull/530))
+An explicitly selected Codex profile's `approval_policy` now takes precedence over the root policy. If you previously relied on a root `never` policy despite a selected profile specifying `on-request`, set the selected profile's policy to `never` to continue denying permission requests. An absent or null profile policy still inherits the root value; Deep Scan workers retain their explicit `never` policy. ([#530](https://github.com/openai/codex-security/pull/530))
<!-- release-section: upgrades:end -->
+
+<details>
+<summary>More improvements</summary>
+
+- Hosted scans pass `reasoningEffort` strings through to the executor, including `max` and future values supported by the selected model or provider. The GitHub Action's `effort` input also accepts provider-supported strings and retains its `xhigh` default. Deep Scan forwards resolved native settings to fresh and resumed workers while retaining worker-specific permissions. ([#1712](https://github.com/openai/codex-security/pull/1712), [#1717](https://github.com/openai/codex-security/pull/1717))
+- Standard and diff scans use available workers and continue review in the parent when delegation is unavailable. Optional worker or goal-tool availability no longer depends on the removed capability registry. ([#1609](https://github.com/openai/codex-security/pull/1609))
+- Patching and fix verification use complete sealed findings from saved scans, preserving current triage and remediation state. Workbench excerpts stay tied to the source and scope of the saved scan, and publishing older findings preserves their historical root-cause details and code evidence. ([#1608](https://github.com/openai/codex-security/pull/1608), [#488](https://github.com/openai/codex-security/pull/488), [#1756](https://github.com/openai/codex-security/pull/1756))
+- Usage reporting distinguishes recorded tokens from missing worker receipts or unfinished turns. Partial totals display as "at least X tokens; some usage unavailable." Saved scan history includes parent/worker totals and measurement times alongside cost estimates; historical account-limit readings are not a live allowance check. See [progress and cost](https://github.com/openai/codex-security/blob/npm-v0.5.0/sdk/typescript/docs/cli.md#progress-and-cost). ([#1640](https://github.com/openai/codex-security/pull/1640))
+- Bulk-scan recovery validates completed artifacts before reusing them and preserves interrupted receipt bytes. Parallel workers serialize receipt writes, and publication replaces its latest receipt atomically. Completed Linear publication results remain available after late cancellation during a failed final receipt write. ([#1720](https://github.com/openai/codex-security/pull/1720), [#1748](https://github.com/openai/codex-security/pull/1748), [#1735](https://github.com/openai/codex-security/pull/1735), [#1738](https://github.com/openai/codex-security/pull/1738), [#1725](https://github.com/openai/codex-security/pull/1725))
+- Matching GitHub Action distributions publish their manifest, SBOM, and full distribution commit SHA in a companion `action-vX.Y.Z` release. Artifact upload failures propagate the original stream error and cancel active streams. ([#1711](https://github.com/openai/codex-security/pull/1711), [#1671](https://github.com/openai/codex-security/pull/1671))
+- Failed or canceled `dedupe --json --full-output` commands no longer print a false success envelope. Diff scans handle root commits in SHA-256 repositories and read blobs with Git versions older than 2.38. ([#1071](https://github.com/openai/codex-security/pull/1071), [#1716](https://github.com/openai/codex-security/pull/1716), [#1715](https://github.com/openai/codex-security/pull/1715))
+- DOCX knowledge-base extraction excludes deleted revisions and field instructions while preserving visible field results. ([#1714](https://github.com/openai/codex-security/pull/1714))
+
+</details>
diff --git a/.prettierrc.json b/.prettierrc.json
new file mode 100644
index 000000000..4bd8bae26
--- /dev/null
+++ b/.prettierrc.json
@@ -0,0 +1,10 @@
+{
+ "overrides": [
+ {
+ "files": ".github/release-notes.md",
+ "options": {
+ "proseWrap": "never"
+ }
+ }
+ ]
+}
diff --git a/RELEASING.md b/RELEASING.md
index 028541b1f..e2c8d0f10 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -2,7 +2,8 @@
[GitHub Releases](https://github.com/openai/codex-security/releases) is the
canonical changelog. Under the current process, each new release combines a
-short, reviewed summary with a categorized list of merged pull requests.
+short, reviewed summary with an expandable categorized list of merged pull
+requests.
Historical releases may contain generated notes only. The release tag and npm
package use the same stable version: `npm-vX.Y.Z` and
`@openai/[email protected]`. Releases whose source includes the GitHub Action
@@ -159,6 +160,28 @@ drafts highlights from merged titles and lists marked breaking changes for
migration review; it does not infer migration instructions from source code.
Review and refine these suggestions before releasing.
+Keep the published notes easy to scan:
+
+- Start with a short overview and the main user-facing highlights. Use bold
+ topic labels to make the bullets easy to skim. Put secondary improvements
+ in a `<details>` block when they would crowd out upgrade guidance.
+- Keep breaking changes and required upgrade actions visible. Long migration
+ procedures can go in a clearly named `<details>` block under the relevant
+ upgrade note. Keep code fences, tables, and lists intact.
+- Keep each prose paragraph or list item on one source line. GitHub Releases
+ renders source newlines as visible breaks, including those before links.
+ The release-note Prettier override uses `proseWrap: "never"`, and the SDK
+ format check includes this file.
+- Leave the complete PR inventory to the publisher. It appends the generated
+ notes, contributor credits, and comparison link in an **All changes**
+ disclosure after the reviewed summary. Releases without a reviewed summary
+ keep their generated notes visible.
+
+Preview both the release list and the individual release in GitHub. Check
+paragraph flow, inline links, tables, code examples, and expanded details.
+Edits to an already published release do not change its immutable tagged
+source; rerunning publication uses that tagged summary again.
+
- Edit the highlights or upgrade notes on the release PR branch. Keep the
surrounding `release-section` comments if you want to retain section
boundaries. The bot refreshes a section only while it matches the last
diff --git a/sdk/typescript/scripts/check-markdown.mjs b/sdk/typescript/scripts/check-markdown.mjs
index b06f20fda..e709d5985 100644
--- a/sdk/typescript/scripts/check-markdown.mjs
+++ b/sdk/typescript/scripts/check-markdown.mjs
@@ -10,6 +10,7 @@ const files = execFileSync(
"ls-files",
"-z",
"--",
+ ".github/release-notes.md",
":(glob)sdk/typescript/**/*.md",
":(glob)examples/custom-validation/*.md",
":(glob)plugins/codex-security/native/*.md",
diff --git a/sdk/typescript/scripts/release-automation.mjs b/sdk/typescript/scripts/release-automation.mjs
index 8920a0f99..39f6611ef 100644
--- a/sdk/typescript/scripts/release-automation.mjs
+++ b/sdk/typescript/scripts/release-automation.mjs
@@ -139,7 +139,12 @@ export function composeReleaseNotes(generatedNotes, releaseSummary) {
releaseSummary,
releaseSummaryEnd,
"",
+ "<details>",
+ "<summary>All changes</summary>",
+ "",
generatedNotes,
+ "",
+ "</details>",
].join("\n");
}
diff --git a/sdk/typescript/tests-ts/release-automation.test.ts b/sdk/typescript/tests-ts/release-automation.test.ts
index a88ff3c10..c812f3563 100644
--- a/sdk/typescript/tests-ts/release-automation.test.ts
+++ b/sdk/typescript/tests-ts/release-automation.test.ts
@@ -729,12 +729,24 @@ describe("reviewed release note helpers", () => {
});
test("composes reviewed and generated notes deterministically", () => {
- expect(composeReleaseNotes("Generated notes", "Reviewed summary")).toBe(
- "<!-- codex-security-release-summary:start -->\n" +
- "Reviewed summary\n" +
- "<!-- codex-security-release-summary:end -->\n\n" +
- "Generated notes",
- );
+ const summary = "## Highlights\n\nReviewed summary";
+ const generated = [
+ "## What's Changed",
+ "",
+ "- A change ([#1](https://github.com/example/project/pull/1))",
+ "",
+ "## New Contributors",
+ "",
+ "- @contributor",
+ ].join("\n");
+ const notes = composeReleaseNotes(generated, summary);
+ expect(extractHistoricalReleaseSummary(notes)).toBe(summary);
+ expect(notes.indexOf(summary)).toBeLessThan(notes.indexOf("<details>"));
+ expect(notes).toContain(`</summary>\n\n${generated}\n\n</details>`);
+ expect(notes.match(/<details>/gu)).toHaveLength(1);
+ expect(
+ composeReleaseNotes(generated, extractHistoricalReleaseSummary(notes)),
+ ).toBe(notes);
expect(composeReleaseNotes("Generated notes", null)).toBe(
"Generated notes",
);