Skip to content

chore(release): cut v0.29.0 changelog entry - #855

Merged
fas89 merged 1 commit into
mainfrom
chore/release-cut-v0.29.0
Nov 12, 2026
Merged

fas89 merged 1 commit into
mainfrom
chore/release-cut-v0.29.0

Conversation

@fas89

@fas89 fas89 commented Nov 12, 2026

Copy link
Copy Markdown
Collaborator

Description

This cuts the 0.29.0 release notes. ## [Unreleased] moves under ## [0.29.0] — 2026-11-12, with an empty [Unreleased] above it. The founder asked for this release in session chat on 2026-11-12. Once this merges and ci.yml passes on the merge commit, v0.29.0 gets tagged and release.yml publishes it.

release.yml's own awk extractor, run on [0.29.0], finds 22 entries under Added, Changed, Fixed and Security. Since v0.28.0 the release contains:

Two corrections make the notes accurate:

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would break existing functionality)
  • Documentation update
  • Refactor / code cleanup
  • New provider or provider enhancement

Documentation

Checklist

  • I have read the Contributing Guide
  • My code follows the project's coding standards
  • I have added tests that prove my fix/feature works
  • All new and existing tests pass (pytest)
  • I have run ruff check and black with no errors
  • New maintained Python files include license headers (python scripts/add_license_headers.py; examples/** exempt)

Testing

  • release.yml's extractor finds 22 entries under 4 headings, and [Unreleased] is empty.
  • product_guardrail passes, both in self-test and on the canon.
  • detect-secrets-hook on CHANGELOG.md exits 0.
  • The tests that read the CHANGELOG pass: 45 passed, 4 skipped.
  • An open Trello card mentions 0.29.0, the deptry card, but it is in Done, so nothing gates the cut.

Moves [Unreleased] under [0.29.0] — 2026-11-12, leaving an empty
[Unreleased] above it. release.yml extracts this section as the GitHub
Release body: 22 entries under Added, Changed, Fixed and Security.

Two corrections ride along so the release notes are accurate:
- #854 merged without a CHANGELOG change. Its three entries are added:
  runs without a terminal use the saved fluid ai setup choice, --agent
  stdout carries only the JSON-Lines events, and fluid mission run no
  longer picks a coding agent it cannot use.
- #852's no-provider entry quoted a "does not read the saved choice"
  variant that #854 replaced; it now names the saved coding agent the run
  passes over.
@fas89
fas89 merged commit 802ffed into main Nov 12, 2026
33 checks passed
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.

1 participant