Skip to content

Update dependency aqua:ctxrs/ctx to v1.4.10 - #687

Merged
timmo001 merged 1 commit into
distro/arch-omarchy-quattrofrom
dot-renovate/timmo001/aqua-ctxrs-ctx-1.x
Sep 18, 2026
Merged

timmo001 merged 1 commit into
distro/arch-omarchy-quattrofrom
dot-renovate/timmo001/aqua-ctxrs-ctx-1.x

Conversation

@timmo001

Copy link
Copy Markdown
Owner

This PR contains the following updates:

Package Type Update Change
aqua:ctxrs/ctx tools minor 1.3.1 → 1.4.10

Release Notes

ctxrs/ctx (aqua:ctxrs/ctx)

v1.4.10

Compare Source

Released: 2026-09-16

Fixed
  • Upgrades recognize stopped daemons even when another process has reused
    their process ID.
  • Daemon status no longer requests a restart solely because another shell has
    different locale, temporary-directory, or session settings.
  • Windows manual upgrades and semantic-runtime repairs record completion
    before restarting background indexing. Resume preserves the installed
    environment and data-root path.
  • Windows scheduled tasks wait for fresh daemon ownership when process IDs
    are reused.
  • Hosted installers accept supported existing semantic and named-source settings.
Commits and PRs

v1.4.9

Compare Source

Released: 2026-09-16

Fixed
  • Hosted setup waits for the first searchable history index before completing,
    including when indexing is configured as manual or progress output is
    disabled. Manual mode stays manual after the foreground refresh.
  • Setup no longer reports background indexing as queued when background work is
    disabled. Installer paths that do not start ctx pro print the ctx pro CTA.
Commits and PRs

v1.4.8

Compare Source

Released: 2026-09-16

Fixed
  • Upgrade warnings preserve line breaks in human-readable output while
    escaping terminal control characters. JSON warning values are unchanged.
  • On Linux, when systemd reports that the ctx user service has hit its start
    limit, ctx clears that service's failure state and retries the start once.
    Other failures do not trigger a reset, and daemon ownership checks still
    apply after the retry.
Commits and PRs

v1.4.7

Compare Source

Released: 2026-09-15

Fixed
  • On Linux, daemon status reports a responsive daemon as running when ctx
    cannot inspect its executable, with executable identity marked unavailable.
    If the daemon does not respond, its owner remains unverified instead of
    being reported as a stale lock.
  • Imports and waits can keep using an authenticated connection to a matching
    daemon when executable inspection is denied. Denied inspection does not
    trigger a service handoff or allow forced termination.
Commits and PRs

v1.4.6

Compare Source

Released: 2026-09-15

Changed
  • Background refresh diagnostics distinguish supported filesystem and resource
    failures using typed causes, without collecting paths or error text.
  • Telemetry upload recovery reports distinguish supported connection, timeout,
    response-read and local queue failures. Older clients can continue sharing
    the same queue. Unknown causes remain unspecified; retry behavior is unchanged.
Fixed
  • In 1.4.6, managed installation, upgrade and uninstall accept user-owned 755 and
    775 executable directories and preserve their permissions and unrelated
    tools. The shell installer no longer changes an existing bin to 700.
  • Installer failures stop progress output before showing the error and tell
    users to resolve the reported problem before retrying.
    Already-installed older CLIs still apply their old permission checks during
    upgrade; their errors are now shown without changing shared directory permissions.
  • On Linux, ctx pro credentials use the existing /run/user/<uid> session
    directory when XDG_RUNTIME_DIR is unset.
Commits and PRs

v1.4.4

Compare Source

Released: 2026-09-15

Fixed
  • File filters recognize literal filenames from Codex tool arguments encoded
    as JSON strings and from direct or nested patch headers. Original content
    is preserved, and available source logs are reparsed for existing indexes.
  • Background refresh diagnostics preserve typed coverage-block reasons
    through recovery and retain complete partial-source classifications,
    without changing refresh or retry behavior.
  • Updated rustls to 0.23.45 to enforce TLS 1.3 handshake encryption boundaries
    (RUSTSEC-2026-0285).
Changed
  • Repository-local Rust toolchain settings consistently select Rust 1.97.1.
    The declared minimum supported Rust version remains unchanged.
  • Windows source-build instructions explain the MSVC C++ tools, Windows SDK
    and Bash prerequisites, which are not needed for prebuilt installations.
Commits and PRs

v1.4.3

Compare Source

Released: 2026-09-14

Fixed
  • History on tmpfs and supported eCryptfs encrypted-home filesystems can be
    indexed. eCryptfs requires an inspectable backing filesystem that meets the
    existing local-filesystem requirements.
  • Rejected source roots retain their filesystem or permission error instead
    of being reported as symlink problems. ctx doctor JSON now reports
    incomplete source discovery, matching the human-readable output.
  • ctx doctor no longer recommends retrying a completed import solely because
    some records were rejected.
  • MCP clients can list event metadata when an event is too large to inline.
Changed
  • Failed background refreshes retain coarse failure-stage and error-family
    diagnostics. These do not include error text or paths, change retry behavior,
    or retroactively diagnose earlier failures.
Commits and PRs

v1.4.2

Compare Source

Released: 2026-09-12

Fixed
  • Fixed a macOS folder-watcher shutdown race that could leave background
    refresh stuck while the list of watched folders was being updated.
  • Background refresh on macOS now detects appended history even when a folder
    notification is missed.
  • Readers and recovery processes prepare their file limits before opening an
    index. Stalled refresh requests return an actionable error instead of waiting
    indefinitely, and ctx doctor explains disk-space and file-limit failures.
  • Semantic search keeps large source catalogs within the manifest size limit
    and reports runtime startup failures instead of showing continued preparation.
  • Fixed SQLite lock handling during Semantic indexing and local usage recording.
  • Codex imports preserve oversized prompts and history after a revert. Goose
    imports accept database versions 9, 15 and 16, and Cursor imports retain
    native turn timestamps.
  • Fixed Cargo subprocess-test compilation.
Commits and PRs

v1.4.1

Compare Source

Released: 2026-09-10

Fixed
  • Restores the telemetry recovery fix from 1.3.2 that was missing in 1.4.0.
    After reporting a partial backlog, the client now reports recovery when the
    remaining events finish sending, including after a restart.
  • Restores installation and recovery guidance, including PATH checks, retry
    commands, custom install locations, and the distinction between installing
    the companion and activating Pro.

The original update feed remains frozen at the 1.3.2 bridge. Current managed
installations receive 1.4.1 through the newer feed.

Commits and PRs

v1.4.0

Compare Source

Released: 2026-09-09

Changed
  • The seven in-repo SDKs now use agent-history-v2, with schema version 1.
    The generic localOnly status property is removed. CLI status and setup JSON
    use schema version 3; generic usage/error, index and daemon envelopes use
    schema version 2. Update consumers that require the old field or check these
    versions; the migration guide
    covers the affected APIs. Operation-specific Semantic diagnostics retain
    their execution-location information.
Fixed
  • Semantic search shows and cites the passage that earned the result's score.
  • Semantic document chunks no longer lose their final tokens to tokenizer
    truncation.
  • Codex imports preserve distinct item and tool-call identities when both are
    present in a transcript.
  • Failed index rebuilds clean up their abandoned candidate files. Disk-pressure
    reports use the observed free space.

GitHub downloads contain unmanaged Core-only binaries. The
hosted installer installs the managed Core and Pro pair.
Existing managed installations move through the 1.3.2 bridge before 1.4.0.
Windows 0.25.0 users must stop any opted-in legacy ctx daemon and rerun the
PowerShell installer.

Commits and PRs

v1.3.2

Compare Source

Released: 2026-09-09

ctx 1.3.2 improves managed upgrades, refresh recovery, Windows installation,
and Semantic packaging while retaining the existing JSON and SDK interfaces.

Changed
  • Stable managed releases now require the complete source-bound semantic model
    and runtime asset set before stable metadata can advance.
  • Existing managed installations upgrade through 1.3.2 before moving to later
    stable releases. Ordinary ctx upgrade handles the transition, except on
    Windows 0.25.0: rerun the PowerShell installer
    because that old executable's self-upgrader cannot complete the update.
    Stop any opted-in legacy ctx daemon before reinstalling.
  • The legacy local_only JSON and localOnly SDK fields remain available but
    are deprecated. Use operation-specific Semantic diagnostics to understand
    execution location; the legacy marker is not a network or privacy guarantee.
Fixed
  • Managed Core and Pro upgrades preserve a truthful applied result and recover
    safely when post-commit finalization or restart work is interrupted.
  • Windows managed-pair replacement now handles access-control changes,
    candidate cleanup, and path identity correctly.
  • Windows installers preserve command exit codes and diagnostic output in
    PowerShell 5.1 and 7, including successful commands that write to stderr.
  • The PowerShell installer recovers managed Windows 0.25.0 installations using
    the authenticated release, without relying on the old broken self-upgrader.
  • Windows background processing handles private-directory permissions and
    concurrent readers correctly.
  • Refresh restart recovery preserves source-authoritative predecessor rebuilds
    and retained readers without reviving obsolete protocol paths.
  • Refresh jobs report completion only after the terminal journal write is
    confirmed; an unconfirmed write remains pending for retry.
  • Telemetry reports recovery once queued events finish sending, including
    when delivery resumes after a restart.
  • Installer downloads and decompression have bounded work and preserve useful
    failures instead of hanging indefinitely.
  • Managed-pair protocol output and automatic-upgrade warnings again follow
    terminal output ownership, including raw and machine-readable modes.

GitHub Release downloads are unmanaged ctx Core-only binaries; the hosted
installer at ctx.rs/install provides the managed Core
and Pro installation path.

Commits and PRs

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@timmo001
timmo001 merged commit c5b59e0 into distro/arch-omarchy-quattro Sep 18, 2026
22 checks passed
@timmo001
timmo001 deleted the dot-renovate/timmo001/aqua-ctxrs-ctx-1.x branch September 18, 2026 17:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant