Skip to content

Fix tombstones always being marked as ST2#463

Merged
kaste merged 2 commits into
gh-pagesfrom
rips-are-not-st2-always
Jul 22, 2026
Merged

Fix tombstones always being marked as ST2#463
kaste merged 2 commits into
gh-pagesfrom
rips-are-not-st2-always

Conversation

@kaste

@kaste kaste commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

Infer Sublime Text compatibility once and derive the ST2/ST3 labels,
outdated flag, and st3_only flag from that value. Let empty release
lists produce unknown compatibility, which avoids inferring ST labels
for skeleton tombstones.

Otherwise we have:

image

st3_only was unused so I drop it from the search index/db. 🤞 that this doesn't break
anything. Just reload.

kaste added 2 commits July 22, 2026 14:23
Infer Sublime Text compatibility once and derive the ST2/ST3 labels,
outdated flag, and st3_only flag from that value. Let empty release
lists produce unknown compatibility, which avoids inferring ST labels
for skeleton tombstones.
Remove the st3_only boolean from package metadata, the compact search
index, MiniSearch stored fields, and compatibility tests. The ST3 synthetic
label remains the user-visible state.
@kaste
kaste enabled auto-merge July 22, 2026 12:25
@kaste
kaste merged commit 171aca9 into gh-pages Jul 22, 2026
2 checks passed
@kaste
kaste deleted the rips-are-not-st2-always branch July 22, 2026 12:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant