Skip to content

Release v0.7.30: tree-sitter 0.26.0 pin and changes since v0.7.29 #1924

Closed

Description

@ViperJuice

Tracks the phase-loop-runtime 0.7.30 release. Source preparation is in PR agent-harness#1923 (draft).

Why

0.7.29 pins tree-sitter==0.25.2 exactly. Consiliency dotfiles' shared tooling lock also carries treesitter-chunker 6.0.0, which needs tree_sitter>=0.26,<0.27, so dotfiles cannot adopt 0.7.29. 0.7.30 moves the exact pin to tree-sitter==0.26.0. tree-sitter-typescript stays ==0.23.2, and both pins stay exact (agent-harness#1765).

The release also ships main since v0.7.29: agent-harness#1911, agent-harness#1914, agent-harness#1917, agent-harness#1922, agent-harness#1904, agent-harness#1918 and agent-harness#1919.

Release gates

  • Source preparation: version bump, CHANGELOG, v10 roadmap anchor and digests, manifest authority rows (agent-harness#1923; package-source commit f64b8780).
  • Publishing tests on CPython 3.12 (uv, frozen) and the system 3.14.4: 166 passed on each.
  • One live agy 1.3.5 qualification of f64b8780 on ai; the regenerated record committed on top as a non-source commit.
    • 2026-11-08 14:37Z: the preflight failed on I/O PSI (5.2 against < 5). No live run.
    • 2026-11-08 14:46Z: the preflight passed, but the run stopped at the login gate. The Gemini login on ai is expired, and by owner ruling it is not renewed by the agent.
  • Release-mode verify_qualified_agy_image.py --source-only with zero drift, and --route-core.
  • Owner: publication (tag and publish-pypi.yml).

Activity

  1. ViperJuice commented on Nov 8, 2026

    @ViperJuice
    CollaboratorAuthor

    Source preparation PR is agent-harness#1923. Its head is now 2a80358, which adds the non-source manifest-authority commit on top of package-source commit f64b878. The live agy qualification is blocked: the Gemini login on ai has expired, and only the owner may renew it.

  2. ViperJuice commented on Nov 16, 2026

    @ViperJuice
    CollaboratorAuthor

    Reconciliation: phase-loop-runtime 0.7.30 is published. Tag v0.7.30 points to a5b2e147. PyPI upload was at 2026-11-08T18:21:05Z; the file sha256 prefixes are 32e75892f637 and cd531f1e3609. The release has since been superseded: 0.7.34 is published, and it is installed on dev0 through the dotfiles nightly of 2026-11-16 with lock hashes matching PyPI. This closes the release tracking only. It makes no claim of runtime qualification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions