Skip to content

Orion Code v0.3.25 — Four Open-Issue Fixes

Choose a tag to compare

View all tags
@Linux2010 Linux2010 released this 13 Oct 14:57
· 24 commits to main since this release
v0.3.25
c356323
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Orion Code v0.3.25 — Four Open-Issue Fixes

@orion-agents/orion-code@0.3.25 · npm latest · tag v0.3.25 → c356323 (#273)

Closes #269, #270, #271 and #272.

Fixed

  • #269 — Git conflict view fails after editing a conflicted file before staging.
    The worktree version of a conflict was read via hash-object (without -w) and
    then cat-file: the computed OID only exists in the object database while the
    working file is unmodified, so any real edit failed the whole
    GET /api/v1/git/conflict response. The working file is now read from the
    filesystem, contained within the repository root, with the same size bound,
    binary detection and LFS-pointer handling as the object reader; stage reads and
    the read-only contract are unchanged.
  • #270 — File history ignores the requested revision. fileHistory() validated
    rev and used it only for a rev-parse existence check, so every query walked
    HEAD. The validated revision now reaches the git log command.
  • #271 — Model switching skips compact preflight. Both switch paths compared raw
    context windows while the safe input budget (window − output reserve − safety
    margin) existed one line below. Switching to a model with the same or larger
    window but a larger output reserve now reports compactRequired and runs the
    preflight (issue scenario: 100k window, reserve 4k → 48k, history between the
    two budgets).
  • #272 — Left project navigation reshuffles on activation. The workspace registry
    persists a registeredAt timestamp per project (deterministic backfill for
    existing documents), orders pinned projects first and unpinned projects by
    registration order, and exposes it additively on WebWorkspaceSummaryV1.
    Activating a session no longer promotes its project to the top; pinned behavior
    is unchanged.

Changed

  • Release hygiene: the CHANGELOG/READMEs now state the v0.3.24 published facts
    (restoring main's release:check gates) and open the 0.3.25 candidate section.

Quality

Gate Result
Release gate (release:check) PASS
Web E2E critical journey ×3 (Node 22/24/26) PASS
Web E2E full suite three consecutive runs (3×105 scenarios) PASS (one pass)
Node 22/24/26 verification matrices PASS
Full Jest 4505 passed (10 new regression tests)
tarball SHA-256 93e82d4352beada3d315589f527a25d4e4014e960dfb32f70e321ee25b75cc00 (matches the CI three-consecutive-runs artifact exactly)

Install:

npm install -g @orion-agents/orion-code@latest
orion --version   # 0.3.25
Assets 2
Loading