Skip to content

Releases

v1.5.0

Choose a tag to compare

@github-actions github-actions released this 13 Oct 18:35
a4ae09b

Added

  • STANZA_NET_TIMEOUT (seconds, default 120; 0 for no limit) bounds every
    git and gh call that reaches the remote, so a connection that never opens
    costs two minutes at most instead of curl's five, and gh calls can no longer
    wait forever. A read that hits the bound is tried once more before it is
    reported.
  • SSH remotes get a ConnectTimeout of STANZA_NET_STALL_SECONDS beside the
    keepalives, unless you chose your own ssh command.

Changed

  • When a push fails, stanza reads the remote and says
    whether it landed (pushed, not pushed, or unknown) instead of stating
    that nothing was pushed, and the retry or resume hint follows the answer. A
    failed gh pr create or gh pr merge is checked the same way, and an
    interactive prerelease push that landed counts as pushed.

v1.4.1

Choose a tag to compare

@github-actions github-actions released this 11 Oct 12:03
1c53c99

Added

  • CI runs the test suite on every push and pull request to dev and main:
    on Linux, on macOS's own /bin/bash 3.2 (the oldest bash stanza supports),
    and through ShellCheck, which now reports no findings in the shipped
    scripts. tests/run.sh is the one entry point for CI and for local runs.
  • A test matrix holds every command with a JSON shape to its output contract
    under each verbosity, in text and --json mode, on success and on failure.

Changed

  • stanza init and stanza rules print a failure document on stdout under
    --json ("ok": false, with error and hint), as stanza release
    does, and their success documents carry "ok": true. They used to print
    nothing on stdout when they failed.
  • stanza release under --json prints its failure document for a usage
    error too (an unknown option, a missing bump type), with failed_step
    "preflight".
  • The "Use -h or --help" line after an unknown option goes to stderr, so it
    no longer lands ahead of the JSON document on stdout.

v1.4.0

Choose a tag to compare

@github-actions github-actions released this 11 Oct 08:51
f98220d

Added

  • stanza release --check runs the release's preflight checks and changes
    nothing: exit 0 when the release could go ahead, 1 with every failure when
    it could not.
  • A release that stopped before its tag resumes with one command, where it
    used to need commands typed by hand. Re-running stanza release <type> or
    stanza release pr <type> after a failed push or pr step finds the bump
    already on dev and pushes it and opens the PR instead of bumping again.
    stanza release merge after the PR merged but before the tag finds the
    merge commit on the base branch (the merge of dev's head, with dev's
    tree) and tags it. The full and pr JSON documents carry resumed.

Changed

  • A release checks everything its phase needs before its first commit, push,
    merge, or tag, and reports every failed check in one run. New checks catch
    what used to stop a release halfway: a target tag that already exists in
    this clone or on origin (which left the base branch merged and untagged), a
    target below the latest version tag, a missing base branch on origin, and
    with --no-pr a local base branch that has diverged from origin's (which
    stopped the merge after the bump was pushed).
    With --json, the failure document lists every failure in errors.

Fixed

  • stanza release merge finishes a --local release against the remote. It
    used to stop on a refused git fetch origin main:main, because the local
    base branch carried the release merge that origin lacked, and its resume
    hint repeated the same command. It now pushes the base branch and the tag
    together (git push --atomic), and refuses with a clear error when the base
    branch has diverged from origin's or carries commits after the tag.
  • A failed read of the release's checks no longer stops the release at once.
    The CI gate retries it, one poll interval apart, and stops only after three
    failed reads in a row, so a network blip such as a TLS handshake timeout no
    longer needs a stanza release merge to resume.

v1.3.0

Choose a tag to compare

@github-actions github-actions released this 11 Oct 03:46
0747955

Added

  • stanza release waits for CI before it merges. The full release and
    release merge poll the release PR's checks, and --no-pr polls the
    workflow runs on dev's head. A failed or cancelled check stops the release
    at a new checks step, with the PR open and nothing merged or tagged; fix it
    on dev, push, and resume with stanza release merge. A repository with no
    checks releases as before. STANZA_CHECKS_TIMEOUT (default 1800 seconds; 0
    for no limit) bounds the wait, and the JSON document reports the result in
    checks.
  • A stable release refuses to bump a dev whose head commit already failed
    CI.
  • --skip-checks merges without waiting for CI and bumps a red dev.

Changed

  • Row labels are bold and colored instead of dim gray, which was hard to read
    on a dark background. stanza commands and the installers' step rows use
    pale green; the rows install.sh and uninstall.sh list before their
    prompt use light blue. Both are 256-color codes. warn, hint, error,
    and done keep their colors.

Fixed

  • install.sh --prefix=PATH put shell completions in ~/.bash_completion.d
    and ~/.zsh/completions when PATH/share did not exist yet. A prefix other
    than ~/.local now keeps them under its own share/, created as needed.

v1.2.2

Choose a tag to compare

@github-actions github-actions released this 11 Oct 02:41
f22922b

Changed

  • install.sh and uninstall.sh print in the same row grammar as
    stanza release: a stanza install header, then one labelled row per file
    or step, with every installed file named by its path before the prompt and
    as it lands. A fresh install prints about 20 lines instead of about 50.
  • Their color follows NO_COLOR, --no-color (new on both scripts),
    TERM=dumb, and CLICOLOR_FORCE, and is off when the output is not a
    terminal, so a piped or logged install carries no escape codes.
  • The PATH hint names the user's own startup file (~/.zshrc; for bash,
    ~/.bash_profile on macOS and ~/.bashrc elsewhere; fish_add_path for
    fish), and so do the completion hints when the fallback directories are used.
  • Every installer error says whether anything was installed and is followed by
    a hint row with the next step.

Fixed

  • stanza commands printed their header, rows, and done row without color
    even on a terminal: the color check ran inside a command substitution, where
    stdout is a pipe. They now show the bold header, dim labels, and green
    done the row grammar intended.

v1.2.1

Choose a tag to compare

@github-actions github-actions released this 10 Oct 20:40
95bc808

Changed

  • install.sh refuses to download from a repository URL that is not HTTPS
    (STANZA_REPO_URL=http://...), and its curl downloads require HTTPS and
    TLS 1.2 for the request as well as the redirect.
  • The release-asset workflow no longer leaves the job token in the
    checkout's git config while the release script runs.

v1.2.0

Choose a tag to compare

@github-actions github-actions released this 10 Oct 20:23
587413f

Added

  • One-line install without a clone: curl --proto '=https' --tlsv1.2 -fsSL https://raw.githubusercontent.com/gitronald/stanza/main/install.sh | bash.
    Run outside a checkout, install.sh downloads the latest release (or the
    tag given by --version / STANZA_VERSION) and installs from it.
  • Each stable release publishes stanza-<version>.tar.gz and its .sha256 on
    its GitHub release, built by scripts/release-asset.sh from a tag-triggered
    workflow. The one-line installer downloads that asset and refuses to install
    it unless it matches the checksum; tags without an asset (v1.1.3 and
    earlier) are refused, with a pointer to the clone path.
  • install.sh --yes skips the confirmation prompt. A piped install reads the
    answer from the terminal, and fails with a hint to pass --yes when there
    is none.
  • stanza release merge resumes a release that is already merged and tagged:
    it pushes the tag if only the local clone has it, then runs the dev cycle. A
    re-run after the cycle has finished is a no-op.
  • STANZA_NET_STALL_SECONDS (default 30) sets how long a git transfer may stay
    below 1000 bytes/s before it is abandoned; 0 turns the limit off.

Changed

  • A release that stops partway prints a row naming the failed step (bump,
    push, pr, merge, tag, cycle), what it left behind, and the command
    that resumes it.
  • With --json, a failed release prints a JSON document with "ok": false,
    failed_step, completed_steps, error, resume, and hint. Successful
    release documents carry "ok": true, and merge adds resumed.
  • The dev cycle skips the prerelease bump when dev is already past the
    release, and skips the push when origin/dev already matches.
  • For SSH remotes, git calls add ServerAlive keepalives unless an ssh command
    is already configured.

Fixed

  • A stalled HTTPS fetch or push could hang a release indefinitely. Git calls
    that reach the remote now give up after STANZA_NET_STALL_SECONDS without
    progress, unless the user's own http.lowSpeed* config says otherwise.
  • A failed git or gh call ended the run with no message, because its output
    was discarded. The error it printed is now shown, with the command that
    failed.
  • Error details from the branch, clean-tree, and gh login checks went to
    stdout, ahead of any --json document; they now go to stderr.