roadmap: the distribution ledger after 0.6.0 - #80
Merged
Conversation
PyPI and Open VSX are at 0.6.0 and verified against their APIs. JetBrains is uploaded and waiting on moderation, and the VS Code Marketplace still wants its manual upload, which is the surface that falls behind. Zed no longer "needs nothing from us": a reviewer asked on 2026-08-10 for the submodule to point at a commit on main, because the pin named a branch commit that stopped being reachable once that branch was squash-merged and deleted. Repointed at the v0.6.0 commit. The lesson generalises to any future pin, so it is recorded rather than left as a one-off. MELPA's one-month gate passed on 2026-08-14. Their closing note also carried a monorepo preference that the ledger did not record, which changes what to do if the re-opened PR meets resistance.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The paper trail for the 0.6.0 release, recorded once rather than per surface.
Verified against each registry's API rather than assumed:
pyfun-langTwo ledger entries were wrong rather than merely stale: