Skip to content

fix(metadata-protocol)!: a nested-relation filter condition asks the related object its declared exposure (#22737) #32487

fix(metadata-protocol)!: a nested-relation filter condition asks the related object its declared exposure (#22737)

fix(metadata-protocol)!: a nested-relation filter condition asks the related object its declared exposure (#22737) #32487

Triggered via pull request October 11, 2026 08:36
Status Success
Total duration 1m 16s
Artifacts –

pr-automation.yml

on: pull_request
Check PR Size
0s
Check PR Size
Check Changeset
1m 12s
Check Changeset
Auto Label
0s
Auto Label
Fit to window
Zoom out
Zoom in

Annotations

2 notices
Check Changeset: .changeset/22737-relation-condition-target-exposure.md#L0
ADR-0087 exemption (no-migration-prescription): No metadata moves: no spec key, authorable spelling, export or stored shape is removed, renamed or re-shaped, so there is nothing for `objectstack migrate meta` to rewrite. What narrows is one runtime read position: the generic data door stops evaluating a filter condition on a lookup's target object whose existing `enable` declaration already refuses a query of it on every data route, and the remedy is a filter the caller can already write. The other categories are closed on facts: the package publishes (not unpublished); no ADR-0087 id is named or touched (not registered or already-registered); and no exported declaration is removed or narrowed (not runtime-interface-only or type-surface-only).
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"