Skip to content

Reconcile the changelog with everything shipped since v0.0.5 - #363

Merged
davidmckayv merged 1 commit into
mainfrom
changelog-for-the-licence-change
Sep 4, 2026
Merged

Reconcile the changelog with everything shipped since v0.0.5#363
davidmckayv merged 1 commit into
mainfrom
changelog-for-the-licence-change

Conversation

@davidmckayv

@davidmckayv davidmckayv commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

CHANGELOG.md is the release notes, so 0.0.6 publishes whatever ## Unreleased says. I walked the 38 commits between v0.0.5 and main against that section. Seven shipped changes had no entry, including two security ones.

Missing entries, now added

PR What was unrecorded
#329 Audit payloads redacted tool_result but not toolResult, the spelling MCP and computer tool calls use, so those arguments and results were stored verbatim in audit_events.payload
#277 networkPolicy.enabled selected the server and the computers but not the culler pod, and a pod no policy selects keeps the cluster default. The switch left open the one pod that wakes every five minutes holding KEY_ENCRYPTION_KEY and BETTER_AUTH_SECRET
#330 A bracketed IPv6 host in AGENT_ENDPOINT_ALLOWED_HOSTS was normalised differently on each side, so a listed address was refused anyway
#313 TRUSTED_ORIGINS fell back to port 3000 while the app serves on 3010, so OAuth redirects were built against a dead port
#309 Open Generative UI: a Bot can answer with an interface it writes rather than prose, behind OPENBOT_GENERATIVE_UI
#308 The sidebar toggle was never drawn, so the roster was unreachable on a phone
#303 Six link-styled buttons lost role="button" and Space-key activation

The two security ones are worth surfacing in notes rather than leaving buried: #329 means an existing trail still holds unredacted tool arguments, which the entry says explicitly, and #277 means a cluster that turned network policies on was not as fenced as it looked.

Deliberately not recorded

#348, #300, #320 and #307 touch only README.md or a CI workflow. The changelog's own rule is that a line belongs when a deployment behaves differently, and a README typo does not qualify.

Also in here

Two lines in docs/releasing.md that #362 made false and my grep missed, because they say "licence" in prose rather than naming the env var:

  • "loadConfig refuses to start without a licence" — it refuses without the Intelligence values; a licence is no longer among them
  • "a step a person takes, on a machine with a licence" — with real Intelligence credentials

Docs and changelog only. No code.

…rrect two docs that still required a licence
@davidmckayv
davidmckayv force-pushed the changelog-for-the-licence-change branch from c12de92 to c10d9c9 Compare September 4, 2026 16:25
@davidmckayv davidmckayv changed the title Add the changelog entry for the licence change, and correct two docs that still required one Reconcile the changelog with everything shipped since v0.0.5 Sep 4, 2026
@davidmckayv
davidmckayv merged commit 3b6e8ea into main Sep 4, 2026
13 checks passed
@davidmckayv
davidmckayv deleted the changelog-for-the-licence-change branch September 4, 2026 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants