Skip to content

prodockit 0.36.1

Choose a tag to compare

@buckwem buckwem released this 17 Aug 16:12
· 45 commits to main since this release
a0ca6a8

Two stops in a Windows run against Surrey GitLab, the message that makes a third one diagnosable, and the Zensical pin.

Fixed

The first push no longer forces over a host-created README (#442). A repository created with "initialize with a README" holds a commit the project's history does not, so an ordinary push is rejected. That was answered with --force-with-lease, which GitLab refuses outright on a protected branch - the rule is about the operation, not the target - so the one case the force existed for was also the case most likely to be blocked. The host's commit is now merged in with -s ours: same tree, fast-forward push, nothing forced and nothing overwritten.

The site probe can run on Windows (#443). It discarded the response body into /dev/null, which Windows has not got; curl tries to create the file, fails, and exits 23. The stage reported "could not check ... the probe did not run" about a site that was serving, on every retry.

Changed

The project stage quotes what the host said (#439). A reader who had just created the project saw the same words on every retry with nothing new to work from. The host's own reply distinguishes what the stage cannot: a project at another path, a group you cannot see into, and a key the host will not accept each need something different from you.

Zensical pinned to 0.0.55 (from 0.0.53). The PDF is byte-identical; 23 pages differ by exactly the generator tag and the bundle filename; stylesheets and workers are byte-identical, so nothing rendered changes.

Full notes: changelog