prodockit 0.36.3

Two changes about versions that nothing was watching.

Changed

Pandoc is pinned on Windows, and a differing local pandoc is named (#454). Only Ubuntu pinned it - macOS and Windows took whatever the package manager served, so a machine bootstrap had just set up ran 3.10.2 while every build in this family pins 3.10.1. Pandoc decides how the PDF renders, so that difference is silent by construction: both builds succeed and only the document disagrees.

Windows now installs --version, as Ubuntu always has. macOS cannot - Homebrew has no way to install an old pandoc - so the check says when the local version differs rather than failing, which on that platform would leave a stage no reader could ever clear. A pandoc too old to render correctly still fails, because that one is fixable.

prodockit pins watches prodockit itself (prodockit-template#173). Its absence from the managed set had exactly the consequence the set exists to prevent: prodockit-template sat two releases behind with nothing noticing, and adding it immediately found prodockit-userguide on prodockit[index]==0.21.0, fifteen behind. Moving either needed -p prodockit typed by hand - the step nobody remembers.

Safe in prodockit's own repository, where the name is the project's identity rather than a dependency: the pattern requires a version operator after the name, so name = "prodockit" and the adjacent version are not declarations.

Full notes: changelog