Skip to content

roadmap: VS Code at 0.6.0, and MELPA resubmitted from the monorepo - #81

Merged
simontreanor merged 1 commit into
mainfrom
ledger-melpa
Aug 29, 2026
Merged

roadmap: VS Code at 0.6.0, and MELPA resubmitted from the monorepo#81
simontreanor merged 1 commit into
mainfrom
ledger-melpa

Conversation

@simontreanor

Copy link
Copy Markdown
Owner

Two ledger corrections and one decision recorded.

VS Code Marketplace is at 0.6.0. The upload cleared verification, so all four controlled surfaces are now at the release version. Only the per-release status line was stale; the entry already says the upload is manual on every release, which remains true and is the point worth keeping.

MELPA is resubmitted as melpa/melpa#10189, recipe unchanged, pointing at the monorepo. GitHub refuses to reopen #10094, so a fresh branch off current master is the way back in.

Decision recorded: pyfun-mode.el stays in the monorepo. MELPA's closing comment carried a preference for packages not to live in monorepos. The PR answers it rather than ignoring it: a full bare clone is 3.3 MB, the mode's version is bumped in lockstep with the compiler by RELEASING.md, and a separate repository would mean two places to keep in step for one file, while resetting the soak time the submission had just finished waiting out. If MELPA insists, splitting is still available.

The parked-registries rule also needed a sentence separating an adoption gate, which is what parks nvim-lspconfig and Mason at ~100 stars, from a process rule with a stated way back in, which is what MELPA gave us. Otherwise the ledger reads as if resubmitting contradicted its own rule.

The Marketplace upload cleared verification, so all four controlled surfaces
are at 0.6.0. The per-release status line was the only stale part; the entry
already records that the upload is manual every time, which has not changed.

MELPA is resubmitted as #10189. GitHub refuses to reopen a closed PR here, so
a fresh branch off current master is the way back in. Their monorepo
preference is answered rather than ignored: the repository is 3.3 MB bare, the
mode's version tracks the compiler by RELEASING.md, and a separate repository
would mean two places to keep in step for one file while resetting the soak
time the submission was waiting on.

The parked-registries rule needed a sentence distinguishing an adoption gate,
which is what parks nvim-lspconfig and Mason, from a process rule with a stated
way back in, which is what MELPA gave us.
@simontreanor
simontreanor merged commit 5f53b0a into main Aug 29, 2026
16 checks passed
@simontreanor
simontreanor deleted the ledger-melpa branch August 29, 2026 16:02
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