Skip to content

docs(changelog): v0.8.0 legacy-compat note + filed follow-up #37#39

Merged
intel352 merged 1 commit intomainfrom
chore/release-notes-legacy-compat
Apr 28, 2026
Merged

docs(changelog): v0.8.0 legacy-compat note + filed follow-up #37#39
intel352 merged 1 commit intomainfrom
chore/release-notes-legacy-compat

Conversation

@intel352
Copy link
Copy Markdown
Contributor

Summary

Doc-only follow-up to PR #38 (v0.8.0 release cut). Adds the legacy-compat note + filed-follow-up paragraph that team-lead's release-task spec called for, but which crossed paths with the admin-merge of PR #38 in the original push.

Lands BEFORE the v0.8.0 tag push so the tag's CHANGELOG includes the note.

Branch / SHAs

Diff

 CHANGELOG.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

Adds a ### Notes block under ## [v0.8.0] with two entries:

  1. Plugin dispatch mode: legacy compat. Documents that this release ships under workflow's legacy untyped map[string]any + structpb dispatch. Explains why F7's canonical-shape Outputs are a stopgap for the gRPC structpb boundary. Pins the strict typed-contract migration (workflow v0.19.0-alpha.5+) for v0.9.0.

  2. Filed follow-up: issue Use ref.Name consistently for FirewallDriver.Update error formatting #37ref.Name vs spec.Name consistency in FirewallDriver.Update error formatting (Minor advisory from F7 review, non-blocking, scoped for v0.8.x).

Self-review checklist

Post-merge

After this lands on main, push the v0.8.0 tag pointing to the post-merge commit so the tagged release's CHANGELOG includes the note:

git checkout main && git pull
git tag -a v0.8.0 -m "v0.8.0 — expose: internal, http_port_protocol, firewall target enforcement"
git push origin v0.8.0

🤖 Generated with Claude Code

Per release-task spec from team-lead: documents the plugin dispatch
mode this release ships under (workflow's legacy untyped map[string]any
+ structpb), explains why the F7 canonical-shape Outputs use is a
stopgap, and pins migration to strict typed-contract dispatch
(workflow v0.19.0-alpha.5+) for v0.9.0.

Filed follow-up: #37 — ref.Name vs spec.Name in FirewallDriver.Update
error formatting (Minor advisory from F7 review, non-blocking, scoped
for v0.8.x).

Doc-only change. No code touched. Lands on top of v0.8.0 release commit
(#38) before the v0.8.0 tag is pushed so the tag's CHANGELOG entry
includes the note.

Co-authored-by: Claude <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings April 28, 2026 04:43
@intel352 intel352 merged commit d010c27 into main Apr 28, 2026
4 checks passed
@intel352 intel352 deleted the chore/release-notes-legacy-compat branch April 28, 2026 04:43
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds release-notes clarifications to the v0.8.0 changelog entry so the v0.8.0 tag will include the intended legacy-compatibility and follow-up tracking context.

Changes:

  • Add a new ### Notes section under ## [v0.8.0].
  • Document legacy plugin dispatch/structpb implications and the planned strict typed-contract migration target.
  • Record follow-up issue #37 regarding FirewallDriver.Update error-name consistency.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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