Skip to content
PR Automation

fix(spec): tombstones for keys live in @objectstack/spec 17.7.0 name 18 as their removal version #33281

Sign in to view logs

fix(spec): tombstones for keys live in @objectstack/spec 17.7.0 name 18 as their removal version

fix(spec): tombstones for keys live in @objectstack/spec 17.7.0 name 18 as their removal version #33281

Triggered via pull request October 13, 2026 13:18
@objectstack-fleetobjectstack-fleet[bot]
unlabeled #23186
claude/issue-23145-tombstone-removal-version
Status Failure
Total duration 1m 27s
Artifacts –

pr-automation.yml

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

Annotations

4 errors
Check Changeset
Process completed with exit code 1.
Check Changeset: .changeset/pre/22876-email-template-category-is-system-retired.md#L0
.changeset/pre/22876-email-template-category-is-system-retired.md exists on the merge base and was not added by this PR, so changing or deleting it silently replaces somebody else's release note (#17712). Two things produce this refusal and their remedies are OPPOSITE, so read which one you are before you act. COLLISION -- you and another PR drew the same changeset filename, and yours overwrote theirs. Remedy: rename yours; restore theirs from base. DELIBERATE CORRECTION -- your change may have made this PENDING release note false, and you rewrote it in the same stroke. Remedy: do NOT restore it -- say so on the PR and get it confirmed; restoring it from the base would put the false sentence back.
Check Changeset: .changeset/23103-page-action-row-on-success-and-executor.md#L0
.changeset/23103-page-action-row-on-success-and-executor.md exists on the merge base and was not added by this PR, so changing or deleting it silently replaces somebody else's release note (#17712). Two things produce this refusal and their remedies are OPPOSITE, so read which one you are before you act. COLLISION -- you and another PR drew the same changeset filename, and yours overwrote theirs. Remedy: rename yours; restore theirs from base. DELIBERATE CORRECTION -- your change may have made this PENDING release note false, and you rewrote it in the same stroke. Remedy: do NOT restore it -- say so on the PR and get it confirmed; restoring it from the base would put the false sentence back.
Check Changeset: .changeset/23082-view-data-api-provider-retired.md#L0
.changeset/23082-view-data-api-provider-retired.md exists on the merge base and was not added by this PR, so changing or deleting it silently replaces somebody else's release note (#17712). Two things produce this refusal and their remedies are OPPOSITE, so read which one you are before you act. COLLISION -- you and another PR drew the same changeset filename, and yours overwrote theirs. Remedy: rename yours; restore theirs from base. DELIBERATE CORRECTION -- your change may have made this PENDING release note false, and you rewrote it in the same stroke. Remedy: do NOT restore it -- say so on the PR and get it confirmed; restoring it from the base would put the false sentence back.