Skip to content

roadmap: bring the distribution ledger up to 0.4.0, and park the rest - #55

Merged
simontreanor merged 1 commit into
mainfrom
roadmap/distribution-ledger-0.4.0
Jul 31, 2026
Merged

roadmap: bring the distribution ledger up to 0.4.0, and park the rest#55
simontreanor merged 1 commit into
mainfrom
roadmap/distribution-ledger-0.4.0

Conversation

@simontreanor

Copy link
Copy Markdown
Owner

Fixing the stale refs before we forget them, and then arranging things so there is less to go stale.

Our own surfaces, verified against their APIs rather than from memory:

ledger said actually
Open VSX 0.3.0 0.4.0
VS Code Marketplace no version 0.4.0
JetBrains "0.3.0 awaiting moderation" 0.3.0 approved; 0.4.0 not uploaded

JetBrains 0.4.0 is the one artifact the release still owes. Acceptance is already granted, so gradle publishPlugin is not gated on anything — say the word and I'll run it.

The Marketplace entry now also records that it reports the previous version for a few minutes after an upload while validation runs, so a stale read there is not a failed upload. That cost a few minutes today and will cost them again otherwise.

Third-party registries are parked until there is adoption evidence, rather than re-checked every release. The evidence that this is the right default is that two of them have already said the same thing in different words:

  • nvim-lspconfig (closed) and Mason (withdrawn): new languages need adoption evidence, informally ~100 stars.
  • MELPA (closed 2026-07-19): not a rejection of the recipe, which they had already signed off — they require the Emacs package to live in a public repo for a month, and pyfun-mode.el was five days old. Re-openable from mid-August with the same recipe unchanged. The ledger previously said "PR open", which was wrong for twelve days.
  • Zed and Helix are open and need nothing from us.
  • nvim-treesitter upstream is archived; our validated branch stays parked.

Every one of these has a documented by-hand install path in editors/README.md, so no user is blocked by a registry that has not answered. That is what makes waiting the right move rather than chasing.

Docs only.

The surfaces Pyfun controls are now recorded from their own APIs rather
than from memory: Open VSX and VS Code Marketplace at 0.4.0, and JetBrains
0.3.0 approved — the "awaiting moderation" note was stale, it went through.
JetBrains 0.4.0 is the one artifact the release still owes, and since
acceptance is already granted it is not gated on anything.

The Marketplace entry also records that it reports the previous version for
a few minutes after an upload while validation runs, so a stale read there
is not a failed upload. That cost a few minutes today.

The third-party registries are parked until there is adoption evidence,
rather than being re-checked every release. Two of them have already said
the same thing in different words: nvim-lspconfig and Mason want roughly a
hundred stars, and MELPA closed the recipe on a one-month package-age rule
having already signed the recipe off. Zed and Helix are open and need
nothing from us. Every one of these has a documented by-hand path in
editors/README.md, so no user is blocked by a registry that has not
answered — which is what makes waiting the right move rather than chasing.
@simontreanor
simontreanor merged commit 256e7a8 into main Jul 31, 2026
11 checks passed
@simontreanor
simontreanor deleted the roadmap/distribution-ledger-0.4.0 branch July 31, 2026 20:30
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