Reconcile the changelog with everything shipped since v0.0.5 - #363
Merged
Conversation
davidmckayv
requested review from
MikeRyanDev,
guidovizoso and
tylerslaton
as code owners
September 4, 2026 16:21
…rrect two docs that still required a licence
davidmckayv
force-pushed
the
changelog-for-the-licence-change
branch
from
September 4, 2026 16:25
c12de92 to
c10d9c9
Compare
mxmzb
approved these changes
Sep 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CHANGELOG.mdis the release notes, so 0.0.6 publishes whatever## Unreleasedsays. I walked the 38 commits betweenv0.0.5andmainagainst that section. Seven shipped changes had no entry, including two security ones.Missing entries, now added
tool_resultbut nottoolResult, the spelling MCP and computer tool calls use, so those arguments and results were stored verbatim inaudit_events.payloadnetworkPolicy.enabledselected 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 holdingKEY_ENCRYPTION_KEYandBETTER_AUTH_SECRETAGENT_ENDPOINT_ALLOWED_HOSTSwas normalised differently on each side, so a listed address was refused anywayTRUSTED_ORIGINSfell back to port 3000 while the app serves on 3010, so OAuth redirects were built against a dead portOPENBOT_GENERATIVE_UIrole="button"and Space-key activationThe 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.mdor 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.mdthat #362 made false and my grep missed, because they say "licence" in prose rather than naming the env var:loadConfigrefuses to start without a licence" — it refuses without the Intelligence values; a licence is no longer among themDocs and changelog only. No code.