Skip to content

fix(metadata-protocol)!: a datasource saved through the metadata door may name only its own stored credentials reference #39330

fix(metadata-protocol)!: a datasource saved through the metadata door may name only its own stored credentials reference

fix(metadata-protocol)!: a datasource saved through the metadata door may name only its own stored credentials reference #39330

Triggered via pull request October 30, 2026 00:39
Status Success
Total duration 2m 3s
Artifacts –

pr-automation.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 notices
Check PR Size
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
Auto Label
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
Check Changeset: .changeset/27762-datasource-meta-save-credentials-ref.md#L0
ADR-0087 exemption (no-migration-prescription): No key of any schema is added, removed, renamed or re-shaped, and no export or type changes: `DatasourceSchema` keeps `external.credentialsRef` authorable, and the save door refuses one value of it, a reference the save's own stored row does not hold. A stored row is never re-judged: it is read and served as before, and a save that sends its reference back keeps it. There is nothing for a migration to rewrite and no tombstone; the remedy is a door, the datasource admin door's `secret`, which the refusal names.
Check Changeset
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"