Skip to content

v3.1.0

Latest

Choose a tag to compare

@DanConwayDev DanConwayDev released this 15 Nov 18:52

Expand CI controls and live status, simplify signer and agent workflows, and
improve release delivery, PR handling and security.

Documentation

  • CI watch help explains that provider capacity refusals are automatically
    retried allocation attempts, and directs JSON stream consumers to the
    coordinator workflow outcome before treating a run as failed.

Added

  • Release assets support an optional software_target manifest field and
    release asset add --software-target option, emitted as a T tag and shown
    in asset output. Use it only when clients need to distinguish assets sharing
    a platform and MIME type; most assets should leave it unset.

  • ngit's own release pipeline supports rehearsing its post-release GitHub,
    setup-ngit and documentation updates without publishing, and applying
    reviewed repair code to an existing signed ngit release without rebuilding
    or replacing its binaries.

  • Standalone shell and Windows installers retry other Blossom servers and
    the versioned GitHub mirror when a download fails or its checksum differs,
    verifying the signed hash before extracting any archive.

  • ngit's own tagged releases are now built and published through ngit-ci to
    Nostr/Blossom, with the same verified archives mirrored to GitHub Releases.
    GitHub-built alternatives
    are available only through a manual emergency workflow, with explicit
    fallback names, checksums and build provenance; they are never published
    automatically as releases. New stable mirrors advance GitHub's latest
    release pointer without letting older retries displace them. Maintainer
    restarts retain tag validation and the original artifact bindings. The
    publisher and its secret-free rehearsal use the verified static Linux
    binary from the release set, avoiding a separate CLI build at publication.
    New releases prefer relay.ngit.dev for Blossom downloads, retaining the
    existing replication servers. Stable releases then update setup-ngit on
    Nostr and GitHub, verifying its pins and installer before advancing the
    floating action tag. Publication requires exact-commit manual release prep
    covering Linux Rust CI, macOS tests and all archives. Promote the prepared commit unchanged
    to main and an annotated tag; publication reuses its archive bytes and runs
    NIP-82 then GitHub before independent setup-ngit and docs updates. Generated
    downstream commits use an explicit release-bot identity;
    docs promotion verifies the deployed site and live installer hashes.

  • ngit's release pipeline builds and collects its five portable archives on
    Nostr CI before tagging, including Linux-hosted Windows MSVC
    cross-compilation.
    OpenSSL source is fetched as a pinned Nix input rather than downloaded
    by the archive command inside the build guest.

  • ngit pr applied <ID> --reason ... records acceptance after a missed status
    publication, cherry-pick, or equivalent change without merging or touching
    Git state. Existing status authorization applies; repeated use is a no-op.

  • ngit skill install and upgrade accept --global to install the skill
    for your user account (~/.agents/skills/ngit and ~/.claude/skills/ngit)
    and --system to install it for every user of the machine, in the
    directories agents document reading: /etc/codex/skills/ngit and, on
    Linux, /etc/claude-code/.claude/skills/ngit. NGIT_SYSTEM_SKILLS_DIR
    names a single directory to use instead. Interactive runs (-i) ask which
    scope to use; non-interactive runs keep the repository scope. A first
    repository install asks interactively before adding the ngit instruction
    to existing AGENTS.md/CLAUDE.md files, and --no-agent-file declines
    without prompting. ngit skill status --json reports every scope in a
    scopes object, and install results name their scope. Thanks to
    hzrd149.

  • An optional manual macOS pre-release workflow builds ngit's Apple Silicon
    Nix package and checks its startup, unit tests, and rejection of untrusted Git
    HTTPS certificates before a release is tagged. Trusted Git HTTPS fixture
    checks run on Linux; macOS SecureTransport requires system trust rather than
    the fixture's process-local CA file. Rejection checks require the TLS
    server to select the fixture certificate, not merely a failed clone.

  • --help adds concise, version-matched workflow guidance across ngit's
    commands, written to be token-efficient for AI agents and complement the
    expanded guides in ngit-docs. The bundled skill directs agents to this
    installed guidance instead of carrying separate reference content.
    A top-level task map routes agents to command
    workflows, with shared conventions for JSON, identifiers, signers and
    repository selection. Command help covers rules, pitfalls and copyable
    examples, including plain Git steps; the CLI reference export includes
    these notes too. Help uses compact option listings, 80-column prose and
    colour-terminal styling, while -h stays a short summary. Global options
    and --version are listed at the top level; --json stays visible on
    every command. Piped output, NO_COLOR and JSON mode remain plain text.

  • --json streams compact signer and relay progress as JSON Lines on stderr,
    with immediate waits, retries and failures, aggregate relay outcomes and
    throttled count samples. Shared diagnostics are structured and redundant human
    result summaries are suppressed. Explicit signer pairing emits an actionable
    URI record even with --quiet. Final stdout results remain unchanged; Git
    and external-process output are not yet fully structured.

  • ci status --watch monitors workflow and job progress in an inline terminal
    view without taking over the screen. It exits after all observed workflows
    conclude and 10 seconds pass without updates; pending work or missing evidence
    keeps it open. --follow watches indefinitely. Stopping observation does not
    cancel execution.

  • ci status --watch --json streams compact snapshots and changes with short
    run/allocation references and full identities in initial snapshots.
    Unchanged renewals are suppressed; --full-events retains complete decoded
    events. Redirected human output receives snapshots when events arrive.

  • ci inspect shows detailed CI for HEAD or an explicit --target, including
    steps, logs, artifacts and coordinator trust. An event ID selects exact
    evidence; decoded or raw signed JSON and filters support protocol diagnosis.
    --artifacts retrieves and verifies manifests without downloading their files.

  • ci service status shows repository coordinators, observed runs from the last
    30 days, latest outcomes and dated maintainer request/stop history. Requested
    coordinators remain visible without recent runs. Verified domain identities
    label coordinators; service claims, advertised availability and run
    authorization remain distinct, with supporting evidence in JSON.

  • ci rerun COORDINATOR RESULT [--job JOB] requests a new native attempt from a
    completed result while retaining external dependency bindings. Native trigger
    and rerun requests support per-job environment pins and resource requirements.

  • ci cancel COORDINATOR RUN-ID lets confirmed maintainers request cancellation
    of an exact workflow attempt. --force bypasses job grace periods or escalates
    an earlier request. Publication is not confirmation of termination.

  • ci secrets sends encrypted atomic set/remove updates to a coordinator inbox
    and waits for inventory confirmation. Output distinguishes accepted updates
    from pending confirmation; --confirmation-timeout controls the wait
    (90 seconds by default, zero for publication only).

  • CI supports issue-open/reopen/close and release-publication triggers, keeping
    distinct activity contexts separate even when they share a Git commit.

  • account login --nostrconnect supports URI-based pairing without QR codes or
    terminal input, including named profiles, explicit signer relays and JSON.
    --profile NAME --no-activate saves a signer without changing the active login.

  • account logout --all removes all known saved profiles and credentials and
    clears current-repository and non-local Git login configuration, including
    conditional includes and Windows ProgramData configuration. It does not scan
    other repositories or revoke access at remote signers. --keep-credentials
    clears selections without accessing saved secrets, including locked keyrings.
    Cleanup follows Git include paths, including symlink-relative paths, without
    modifying unrelated configuration files.

  • Configure relay timeouts through nostr.relay-timeout-secs and
    nostr.relay-connect-timeout-secs, or NGIT_RELAY_TIMEOUT_SECS and
    NGIT_RELAY_CONNECT_TIMEOUT_SECS. Defaults remain 45 seconds and the smaller
    of 7 seconds and the long timeout; an explicit connect override is independent.
    ngit --customize documents precedence and scope.

Changed

  • Release archives build only on explicit requests and as part of manual
    release-prep, instead of on every PR or main push. Prepare a release once
    on a maintainer branch, then fast-forward main and tag the exact approved
    commit to publish its existing archives without another build.

  • ngit nsite publish --json uses format version 3: successful uploads are
    summarized with replication totals and actionable per-server problems.
    Use --verbose for the full result.blossom.blobs array from version 2.
    Identical preflight warnings are deduplicated.

  • Build containers with Rust 1.99 on supported Alpine 3.24 and use matching
    OpenSSL development and static libraries plus an explicit runtime CA bundle.

  • Update the isolated Grasp integration-test fixture to v3.1.1, including
    upstream server security fixes. This does not update deployed relays.

  • Refresh Nix package and toolchain inputs, retaining the supported Intel
    macOS package set and pinned formatter. Declare libgit2 explicitly in
    package, development, and CI environments as required by current Nixpkgs.

  • Refresh openssl-sys to 0.9.118. Downloadable archives still require the
    separately pinned OpenSSL build because its source-crate constraint is
    unchanged.

  • ngit release subcommands no longer define their own --json beside the
    global one. The flag is accepted at the same positions and produces the
    same output; these commands now read the global JSON mode, so warnings and
    progress follow it wherever the flag is written.

  • The bundled agent skill (version 1.30) is now a short bootstrap. It tells
    agents to use ngit in repositories with a nostr:// remote, which its
    description also names as Grasp repositories, and to read the
    workflow guidance in the installed ngit --help, including before opening
    or updating a PR with git push, instead of repeating commands and feature
    details that change between releases. The reference files are no longer
    bundled: ngit skill install writes only SKILL.md, and ngit skill upgrade (or install over an existing skill) removes the whole
    reference/ directory left beside it by earlier versions and leaves the
    deletion uncommitted for review. An agent whose ngit predates workflow help is told
    to update it.

  • The recommended way to tell coding agents a repository uses ngit is now a
    short instruction in the root AGENTS.md or CLAUDE.md that sends them to
    ngit --help, with the repository skill as an option. ngit skill --help
    shows the instruction to copy and reword. The maintainer reminder, including
    after ngit init, points there rather than to ngit skill install, and
    stops once one of those files mentions both ngit --help and
    ngit.dev/install or the skill is installed. The upgrade reminder for an
    outdated skill mentions the instruction until a file carries it.
    ngit skill status reports
    the detection as help_instruction. ngit skill install appends this
    instruction, in place of a pointer to the skill file, to existing
    instruction files that do not mention ngit; it still creates none.

  • Credential-store failures include recovery guidance and the underlying cause.
    Login reports missing profiles before incompatible relay options and shows
    how to supply credentials for the named profile.

  • Accept an explicit default branch in ngit send --target-branch and Git
    push target-branch= options, retaining it as the PR target.

  • PRs and PR updates now send the signed event to the selected hint's GRASP
    relay before pushing its Git data. If either step fails, ngit tries the next
    candidate with a newly signed event and its clone hint. Once the hint works,
    a second stage sends the same event to all remaining Nostr relays, including
    GRASP relays, before replicating Git to accepting GRASPs and ordinary Git
    servers. Ordinary relays no longer wait for replica Git pushes. This lets
    overloaded GRASP servers reject unaccepted pushes cheaply and apply publisher
    Web-of-Trust policy before receiving a pack. Server selection, one clone hint,
    serial Git transfers and first-success GRASP-06 fallback are preserved.
    Failover updates are strictly newer than earlier attempts. Cached NIP-11
    capability information selects Git-first ordering for older GRASP servers
    without purgatory support, such as Pyramid. Repository-only routing and
    relay fallback policy also apply to PR admission.
    Parallel repository-GRASP pushes without an explicit hint are future work.
    Publication still waits for auth-required before authenticating, unless
    proactive authentication was explicitly enabled. Public-repository
    AUTH signing is bounded by the configured relay timeout (45 seconds by default)
    and a timeout skips that destination; private/GRASP-08 repositories retain the
    signer's native approval window. Network waits remain bounded in both cases;
    read connections retain their existing demand-auth policy.

  • Bring ngit ci up to date with the forthcoming ngit-ci event shapes and
    controls. Status shows workflow, job and live step progress with readable
    timings, short run IDs and ages. Failed jobs include a direct full-log link
    and a muted └ preview of the last three lines. Inspection adds full execution,
    artifact and trust details with copyable log sections.

  • CI counters use signed job starts and step offsets when available, with
    measured completed-step durations and labelled lower bounds for older events.
    Explicit pending/running states are supported; verified workflow definitions
    supply expected work without predicting conditional outcomes. Workflow headers
    show a ticking duration while running, then age and duration after completion.

  • Current CI stays separate from earlier attempts and previous commits. Earlier
    attempts retain inspection links; only the newest related previous tip appears,
    as a concise workflow summary, when current-tip CI is absent. Shared commits
    alone do not establish a published PR association. Reused results and distinct
    executions such as matrix instances remain identifiable. Coordinator-selected
    retries stay current, with rejected allocations retained as previous attempts.

  • CI trust uses relevant signed evidence without unnecessary identity lookups
    when authorization is already established. Routine relay-refresh and optional
    identity diagnostics stay in verbose output and JSON. Missing authorization
    evidence and integrity problems remain visible.

  • Standing CI controls are now ci service request and ci service stop;
    the old commands remain as deprecated aliases. Native manual triggers rerun
    dependency graphs without emitting the obsolete rerun tag;
    --rerun-dependencies is accepted as a compatibility alias.

  • Relay authentication is deferred until a request receives auth-required:,
    avoiding signer prompts for public reads. Gated requests authenticate and
    retry; --proactive-auth, nostr.proactive-auth, or NGIT_PROACTIVE_AUTH
    restores immediate authentication for eligible relays.

  • Remote signer requests retry automatically with three sends two minutes apart,
    then time out two minutes after the last send. Direct terminal users can press
    r or R to resend and restart the window. JSON, headless and Git-helper
    operations retain automatic recovery without reading recovery keys. Refusals
    stop immediately; initial pairing and waits behind another signer operation
    are bounded to two minutes. Pairing failures retain their causes.

  • Signer progress distinguishes pairing, public-key approval and request delivery,
    shows per-relay connection state and recovery guidance, and retains reminders
    for a second approval. Concurrent requests keep separate reports. JSON and
    redirected progress use
    append-only stderr messages across relay, Git, signer and Blossom operations. Verbose mode retains
    detailed diagnostics; JSON stdout remains structured command output or the
    explicit CI watch stream.

  • Name reusable signer configurations with account login --profile NAME.
    The old --alias spelling, stored bindings and JSON fields remain compatible.
    Login prompts clarify scope and profile replacement; account whoami
    distinguishes active signers, repository overrides and saved accounts.

  • Ordinary logout removes the selected connection and saved profile. Use
    --keep-credentials to sign out without deleting credentials; identity-key
    deletion requires --forget. Locked or unreachable OS stores block deletion,
    and deletion failures leave saved profiles intact. These safeguards also
    apply to --all.
    Repository overrides take precedence over defaults, with explicit --local
    and --global scope controls. Removing shared credentials affects other
    repositories that use them.

  • An explicit npub in account logout or account forget-keys selects all known
    credentials and profiles for that identity; named-profile and credential-entry
    targets remain selective. Saved credentials can be removed without contacting
    a signer. Legacy Git-config connections that cannot be retained automatically
    must be exported before using --keep-credentials.

Fixed

  • ngit send configures upstream tracking after publishing a full local
    pr/ branch tip. Tracking uses the selected Nostr remote and its advertised
    PR name, including after local renames; existing tracking is preserved.
    Patches, partial ranges and ordinary branches do not acquire an upstream.

  • CI trigger reachability warnings describe only locally available signed
    state, without predicting rejection of PR-only commits or telling users
    to repush them. Coordinator policy and object availability decide acceptance.

  • Issue auto-resolution requires a reference immediately after the closing
    verb and stops at prose, so incidental wording in PR cover notes cannot
    close unrelated follow-up issues later on the same line.

  • PR merges refuse behind or diverged local default targets before changing
    refs or saving work, checking published repository state and the selected
    remote. Locally ahead targets remain mergeable.

  • Correct the spelling of "public key" in the NIP-05 lookup progress message.

  • ngit release publish, ngit nsite deploy and ngit container now print
    plain Blossom upload progress lines when stderr is not a terminal (log files,
    CI, scripts, coding agents). With --json, these updates are structured JSON
    Lines on stderr; other diagnostics remain text. Each asset and server
    reports when it starts, how many bytes have been sent (at 10% steps or on
    the next byte event after 15 seconds), retries, and when it finishes or fails.
    Previously the upload was silent until the final replication summary, so it looked like a
    stalled signer. Interactive terminals keep the existing progress bars, and
    --json stdout is unchanged.

  • Concurrent account imports and deletions preserve unrelated credentials and
    public-index updates in JSON storage.

  • Refuse to reassign a known signer alias/profile to another identity while its
    OS credential store is inaccessible, preventing an unexpected identity switch
    when the keyring unlocks. New profiles still support file fallback.

  • Reject unused account login --signer-relay options when selecting saved
    credentials or importing a bunker URL, with guidance for fresh pairing.

  • Resolve abbreviated local commit IDs in --base and Git push base=
    options before interpreting them as PR event prefixes.

  • Named remote-signer profiles can use JSON storage when the OS credential store
    is unavailable, without losing the new connection or binding it to an existing
    default signer. Fresh login replaces the identity's default remote session
    while preserving independent profiles and keys. Failed authentication or
    storage leaves the working selection intact; global login preserves local
    overrides.

  • Incomplete local login selections block signing rather than silently using the
    global identity. Account inventory reports unavailable selections accurately.

  • File-store logout works on headless Unix systems without a session bus or
    installed Secret Service.

  • Bare clone/fetch consumers, including Nix source caches, can load existing
    signers and discover proposal refs. Automatic PR branch visibility remains
    opt-in; this does not provide full bare-repository command or publishing support.

  • Repository state ignores names such as refs/tagsevil rather than treating
    them as genuine refs/tags/ entries.

Security

  • Refresh bundled Mozilla certificate roots to 1.0.12, removing the two
    Buypass roots, DigiCert Trusted Root G4, QuoVadis Root CA 1 G3 and 3 G3,
    and Certigna Root CA in line with upstream trust-store policy. This also
    updates the explicit Android HTTP certificate bundle.

  • Update apk-info to 1.1.1 for upstream malformed-metadata allocation
    and parsing fixes used when inspecting APK release assets. Upstream also
    fixes extraction traversal; ngit does not use that extraction API, and
    this update is not evidence of exploitation in ngit.

  • Update libssh2-sys to 0.3.4 for upstream bounds checks before
    encrypt-then-MAC SSH packet decryption, avoiding a local source backport.

  • Update rustix to 1.1.6 for the upstream extended-attribute buffer
    soundness fix (RUSTSEC-2026-0486).

  • Update libz-sys to 1.1.33 for the upstream build environment disclosure
    fix (RUSTSEC-2026-0418) and bundled zlib 1.4. The previously locked cc
    version predates the environment-copying behavior required by the advisory;
    this update is not evidence that ngit build secrets were disclosed.

  • Update nostr/nostr-sdk to 0.45.6 for an upstream signature-verification cache
    fix. ngit ingests relay events through this path, so clients should update.

  • ngit release publish rejects manifest file paths outside the repository root,
    including absolute paths, .. escapes and escaping symlinks, before opening or
    uploading them. This covers assets, source, notes, icons and images. Explicit
    CLI paths such as --manifest and --notes-file remain allowed to be absolute.

  • Verify signatures of cached update metadata before using it, preventing a
    tampered local cache from directing ngit update to an unrelated release.

  • Cargo-based updates and the standalone installer run from the detected Cargo
    installation root, avoiding repository-local .cargo/config.toml settings
    such as compiler wrappers, linkers and source replacements. User-level Cargo
    configuration still applies.