Skip to content

mise.toml pins banned toolchains estate-wide — python in 543/573 files (249 repos); 59 files still pin deno despite the Deno→Bun ruling #706

Description

@hyperpolymath

Claim

mise.toml files pin banned toolchains estate-wide: python in 543 of 573 files (249 canonical top-level repos, 228 at repo root), and 59 files still pin deno despite the standing Deno→Bun ruling (19 in bulk_update_oikos, 3 metadatastician — remote-confirmed deno = "latest" on metadatastician/selur main — remainder in meta-repos incl. project-ovine, rokur, phi-LAM, harvard-dehallucinator, first-post). flake.nix adds ~7 more repos (candy-crash, coq-jr, k9-ecosystem, panll, polystack, reposystem, social-media-tools).

Relationship to #698

#698 asks the policy question (do dev-env definitions count as banned-language use?) on its original guix.scm cohort. This issue is the full inventory feeding that same decision. Whatever is ruled there governs the python/go/java/node pins here.

Independent of that ruling: the 59 deno pins are actionable today — Deno→Bun is an explicit ruling, not a judgment call. ~59 one-line edits.

First step

If #698 rules (a) exempt: close this with the pin inventory recorded. If (b) or (c): sweep the 59 deno pins first (mechanical), then the python pins per the ruling's scope.

Measured 2026-08-31 during #698 verification (find + grep enumeration over local trees, remote spot-checks; no search-count numbers). Filed per the discoveries-become-issues rule.

Metadata

Metadata

Assignees

No one assigned

    Labels

    auditVerification & compliancescope:estateAffects many or all repos across the estatetech-debtKnown shortcut, drift, or hygiene owed - includes cleanup

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions