docs(changelog): v0.8.0 legacy-compat note + filed follow-up #37#39
Merged
docs(changelog): v0.8.0 legacy-compat note + filed follow-up #37#39
Conversation
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>
There was a problem hiding this comment.
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
### Notessection under## [v0.8.0]. - Document legacy plugin dispatch/
structpbimplications and the planned strict typed-contract migration target. - Record follow-up issue #37 regarding
FirewallDriver.Updateerror-name consistency.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
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
origin/main@554f80df(post-chore(release): v0.8.0 — expose: internal, http_port_protocol, firewall target enforcement #38 merge)c88d4b4041f1f637f28b70b7e4bbc8696b7dbe4dDiff
Adds a
### Notesblock under## [v0.8.0]with two entries:Plugin dispatch mode: legacy compat. Documents that this release ships under workflow's legacy untyped
map[string]any+structpbdispatch. Explains why F7's canonical-shape Outputs are a stopgap for the gRPC structpb boundary. Pins the strict typed-contract migration (workflowv0.19.0-alpha.5+) for v0.9.0.Filed follow-up: issue Use ref.Name consistently for FirewallDriver.Update error formatting #37 —
ref.Namevsspec.Nameconsistency inFirewallDriver.Updateerror formatting (Minor advisory from F7 review, non-blocking, scoped for v0.8.x).Self-review checklist
554f80df)git pull --ff-only origin mainclean before commit + push[v0.8.0]section, immediately after the existing F4/F5/F7 entriesPost-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:
🤖 Generated with Claude Code