-
Notifications
You must be signed in to change notification settings - Fork 0
chore: disallow additional properties in table request schemas #134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -7,6 +7,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 | |
|
|
||
| ## [Unreleased] | ||
|
|
||
| ### Changed | ||
|
|
||
| - chore: disallow additional properties in table request schemas | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This entry omits two breaking changes contained in the same diff. First, Failure scenario: a downstream crate on 0.16.0 builds Fix: record the rename and the |
||
|
|
||
| ## [0.16.0] - 2026-09-03 | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: (not blocking) Add an
### Addedsection for the new surface in this diff.The diff adds
connections_api::set_managed_table_constant_per_key,databases_api::set_database_table_constant_per_key,UpdateManagedTableRequest,ManagedTableConstantPerKeyResponseandJobType::TableConstantsUpdate. The 0.15.0 entry lists new endpoints and models that way at CHANGELOG.md:25-38.Without an
### Addedsection, readers of the release notes never learn that the twoconstant-per-keyendpoints exist.