Skip to content

fix(metadata-protocol)!: a datasource restored or published from a stored body may name only the credentials reference its row holds now #39382

fix(metadata-protocol)!: a datasource restored or published from a stored body may name only the credentials reference its row holds now

fix(metadata-protocol)!: a datasource restored or published from a stored body may name only the credentials reference its row holds now #39382

Triggered via pull request October 30, 2026 02:17
Status Success
Total duration 1m 49s
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/27818-datasource-restore-publish-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 doors that make a stored body active refuse one value of it, a reference the row they write into does not hold now. A stored row is never re-judged at rest: it is read and served as before, and only the write that would make it the active row is judged. 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"