Repository navigation
v0.35.4
apogee — v0.35.4 — 2026-11-17
This release closes two ways a repository could get git to run a program of its choosing, restores the blank lines in the Windows Console, and gets the update check and go install ready for a future v1.0.0.
Improved
- The update check is ready for v1.0.0 — The startup update notice and
apogee updatenow announce v1.0.0 and any other v1.x release newer than yours, skipping only the four burned (withdrawn) versions v1.1.0, v1.7.0, v1.8.0 and v1.8.1. Before, they skipped the whole v1.0.0–v1.8.0 range.
Fixed
- Git no longer runs a helper program a repository names for its remote — In a repository whose own config sets
remote.<name>.vcs, a Fetch or another git tool or action could run a program planted in the checkout, outside the sandbox. apogee now refuses to run git there, and the refusal names the setting. git configwrites that would make git run a program are refused in the terminal — Through theterminaltool, setting or removing in the repository's own configremote.<name>.uploadPackorreceivePack,protocol.alloworprotocol.ext.allow(other thannever), anext::url.<base>.insteadOforpushInsteadOf, or asubmodule.<name>.updatestarting with!is now refused in every mode. Otherprotocol.<x>.allowkeys, ordinary URL rewrites, thenone,rebase,mergeandcheckoutupdate modes,--globalwrites and every read still run.- The Windows Console keeps its blank lines — On Windows, the Console Read pane and the text
console_readandconsole_sendhand the model now keep the empty lines the screen shows, so a freshcmdno longer has its banner glued to its prompt. Console output on macOS and Linux is unchanged.
Docs & install
go install …@latestwill reach v1.x releases — Publishing a release from v1.0.0 up to v1.8.1 now runs a newplaceholderstep, also shown bystatus, that tags the v1.8.1 placeholder on the release sogo install …@latestinstalls it; the release binaries still report the release's own version. For any other version the step reports that it is not needed.- Only four v1.x versions are retracted — apogee's
go.modnow retracts exactly v1.1.0, v1.7.0, v1.8.0 and v1.8.1 instead of the whole v1.0.0–v1.8.0 range, so v1.0.0 and other v1.x numbers can ship. The release tool and the automatic tagging refuse a burned version, and ago.modwhose retractions differ from that list. - Release checks confirm the Go module proxy serves each release —
go run ./cmd/release smokegains agoproxycheck that fails when proxy.golang.org cannot resolve the release's version or marks it retracted, and only warns when@lateststill points at another version. It is skipped on a machine without Go. - The building manual covers the burned versions and cutting v1.0.0 — Its release section lists the four burned versions in place of the old range, describes the new
placeholderstep and whypreparenow refuses (rungit fetch --prune --prune-tagsfirst), and adds runbooks for cutting v1.0.0 and for recovery.
Internal
- The macOS sandbox is tested on a real Mac — Continuous integration now runs the macOS sandbox and single-instance lock tests on a macOS machine for every push and pull request, without holding up a release.