Jonathan M HsiehandClaude Opus 5 1a959990ca refactor(secrets): name the binding field for its delivery mode, cap in Rust ...

`secret_bindings` read as the general record of what a Function needs, but a
`Map<String, String>` keyed on environment-variable name can only ever hold an
env-delivered binding: an accessor binding has no variable to key on. Naming
the field for its delivery mode leaves a later mode a sibling field rather than
a tagged value type, which would break a field already in the identity hash.

The per-Function cap moves from `bind_secrets` to
`Connection::create_function_async`, above the backend dispatch, so it holds
for every language surface rather than only the one that validates first. The
low-level PyO3 entry point reached the wire past the Python check; it no longer
does.

Also corrects a doc comment claiming registration fails when a bound Secret is
absent. Existence is first answered at `add_columns`, by design.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UfmeJ533rQDnPBkMtjerV6

2026-09-15 19:28:55 +00:00

..

lancedb

refactor(secrets): name the binding field for its delivery mode, cap in Rust

2026-09-15 19:28:55 +00:00

tests

refactor(secrets): name the binding field for its delivery mode, cap in Rust

2026-09-15 19:28:55 +00:00

type_tests

fix(python): expose inline types to downstream checkers (#3817)

2026-08-07 17:31:42 +08:00