Repository navigation
Releases
Releases · gitronald/stanza
v1.5.0
Added
STANZA_NET_TIMEOUT(seconds, default 120;0for 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
ConnectTimeoutofSTANZA_NET_STALL_SECONDSbeside 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, orunknown) instead of stating
that nothing was pushed, and the retry or resume hint follows the answer. A
failedgh pr createorgh pr mergeis checked the same way, and an
interactive prerelease push that landed counts as pushed.
v1.4.1
Added
- CI runs the test suite on every push and pull request to
devandmain:
on Linux, on macOS's own/bin/bash3.2 (the oldest bash stanza supports),
and through ShellCheck, which now reports no findings in the shipped
scripts.tests/run.shis 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--jsonmode, on success and on failure.
Changed
stanza initandstanza rulesprint a failure document on stdout under
--json("ok": false, witherrorandhint), asstanza release
does, and their success documents carry"ok": true. They used to print
nothing on stdout when they failed.stanza releaseunder--jsonprints its failure document for a usage
error too (an unknown option, a missing bump type), withfailed_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
Added
stanza release --checkruns 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-runningstanza release <type>or
stanza release pr <type>after a failedpushorprstep finds the bump
already ondevand pushes it and opens the PR instead of bumping again.
stanza release mergeafter the PR merged but before the tag finds the
merge commit on the base branch (the merge ofdev's head, withdev's
tree) and tags it. The full andprJSON documents carryresumed.
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-pra 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 inerrors.
Fixed
stanza release mergefinishes a--localrelease against the remote. It
used to stop on a refusedgit 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 astanza release mergeto resume.
v1.3.0
Added
stanza releasewaits for CI before it merges. The full release and
release mergepoll the release PR's checks, and--no-prpolls the
workflow runs ondev's head. A failed or cancelled check stops the release
at a newchecksstep, with the PR open and nothing merged or tagged; fix it
ondev, push, and resume withstanza 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
devwhose head commit already failed
CI. --skip-checksmerges without waiting for CI and bumps a reddev.
Changed
- Row labels are bold and colored instead of dim gray, which was hard to read
on a dark background.stanzacommands and the installers' step rows use
pale green; the rowsinstall.shanduninstall.shlist before their
prompt use light blue. Both are 256-color codes.warn,hint,error,
anddonekeep their colors.
Fixed
install.sh --prefix=PATHput shell completions in~/.bash_completion.d
and~/.zsh/completionswhenPATH/sharedid not exist yet. A prefix other
than~/.localnow keeps them under its ownshare/, created as needed.
v1.2.2
Changed
install.shanduninstall.shprint in the same row grammar as
stanza release: astanza installheader, 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, andCLICOLOR_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_profileon macOS and~/.bashrcelsewhere;fish_add_pathfor
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
ahintrow with the next step.
Fixed
stanzacommands printed their header, rows, anddonerow 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
donethe row grammar intended.
v1.2.1
Changed
install.shrefuses to download from a repository URL that is not HTTPS
(STANZA_REPO_URL=http://...), and itscurldownloads require HTTPS and
TLS 1.2 for the request as well as the redirect.- The
release-assetworkflow no longer leaves the job token in the
checkout's git config while the release script runs.
v1.2.0
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.shdownloads the latest release (or the
tag given by--version/STANZA_VERSION) and installs from it. - Each stable release publishes
stanza-<version>.tar.gzand its.sha256on
its GitHub release, built byscripts/release-asset.shfrom 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 --yesskips the confirmation prompt. A piped install reads the
answer from the terminal, and fails with a hint to pass--yeswhen there
is none.stanza release mergeresumes 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;0turns 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, andhint. Successful
release documents carry"ok": true, andmergeaddsresumed. - The dev cycle skips the prerelease bump when
devis already past the
release, and skips the push whenorigin/devalready matches. - For SSH remotes, git calls add
ServerAlivekeepalives 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 afterSTANZA_NET_STALL_SECONDSwithout
progress, unless the user's ownhttp.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--jsondocument; they now go to stderr.