Skip to content

docs(changelog): backfill omitted 0.8.1 and 0.9.0 entries #104

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.

Sign up for GitHub

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

Merged
zfarrell merged 1 commit into from
Jul 30, 2026
+28 −0
Merged

docs(changelog): backfill omitted 0.8.1 and 0.9.0 entries #104

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,13 +59,41 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

### Changed

- **Breaking:** databases now report the schema that unqualified table names
resolve to, as a required `default_schema` field on `DatabaseSummary`,
`DatabaseDetailResponse`, and `CreateDatabaseResponse`. Because the field is
required, each type's `new()` gained a `default_schema` parameter:
`DatabaseSummary::new(default_catalog, default_schema, id)`,
`DatabaseDetailResponse::new(attachments, default_catalog,
default_connection_id, default_schema, id)`, and
`CreateDatabaseResponse::new(default_catalog, default_connection_id,
default_schema, id)`. Callers that construct these types (or match on them
exhaustively) must supply it; callers that only read them are unaffected.
- feat(databases): add fork endpoint
- chore(api): exclude datasets from public OpenAPI spec + docs cleanup

### Added

- `CreateDatabaseRequest` gains an optional `default_schema` field, naming the
schema unqualified table names resolve to inside the new database's query
scope. When omitted, a database declaring exactly one schema adopts that
schema; otherwise unqualified names resolve to `main`.
- `AddManagedTableDecl`, `AddManagedTableRequest`, and
`DatabaseDefaultTableDecl` gain an optional `key` field naming the columns that
uniquely identify a row. Declaring a key enables the key-based load modes
(`delete`, `update`, `upsert`) on that table, which match rows by those
columns; a table declared without one accepts only `replace` and `append`.

## [0.8.1] - 2026-07-09

### Changed

- **Breaking:** `LoadManagedTableRequest` can now load from a persisted query

@claude claude Bot Jul 30, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

super nit: (not blocking) The published GitHub Release notes for v0.8.1 and v0.9.0 won't pick these up. .github/workflows/release.yml checks out ref: ${{ env.RELEASE_TAG }} (line 37) and extracts notes from the CHANGELOG at that tag, so a workflow_dispatch re-run for v0.8.1 would re-render the old, pre-backfill section — and make_latest: true (line 78) would additionally re-point "latest" at an old tag. Since the point of the backfill is that affected callers were never told, it's worth editing those two release bodies by hand after merge.

result as well as an upload, so `upload_id` became optional and moved out of
the constructor: `new(mode, upload_id)` is now `new(mode)`. Set `upload_id` or
`result_id` on the returned value — exactly one is required. Note this shipped
in a patch release, which Cargo treats as compatible with 0.8.0 for a `0.x`
crate, so it could surface on `cargo update` rather than an explicit upgrade.
- feat(tables): support loading from query results
- feat(databases): expose created_at on list and detail endpoints

Expand Down
Loading