The packer’s command-line entry check constructed a file:// URL by joining a prefix to the resolved script path. That happened to match Node’s module URL on POSIX, but a Windows drive-letter path produced a different URL. The packer then silently exited successfully without generating wekan-real-files.h, and the C compiler failed because that header did not exist.

The entry check now uses Node’s platform-aware path-to-file-URL conversion. Its regression test requires that conversion and rejects the Windows-incompatible hand-built URL, alongside the existing manifest, generated-header and workflow checks.

WeKan v11.50 was built from .meteor/release, which contained METEOR@3.5.2-rc.0, but wekan.fi/version.txt reported 3.5.2-beta.0. The website generator did not read the build pin; it read a duplicated METEOR_RELEASE value in Dockerfile, and that copy had not changed when Meteor advanced from beta to release candidate.

The manifest now reads .meteor/release directly, while every release bump also synchronizes Docker’s runtime metadata from that canonical file. Current Docker metadata is corrected to 3.5.2-rc.0. Regression coverage deliberately gives the generator a stale beta Dockerfile beside an rc Meteor pin and verifies both version.txt and the install page publish the rc version.

release-all.yml previously trusted that version.sh had found and rewritten every copy before committing the bump. A missed pattern could therefore pass silently and be consumed later by one platform or the website. The bump job now runs one shared, read-only consistency gate before its commit step. It verifies the WeKan version in package.json, both package-lock roots, Docker, Snap, Stacker and Sandstorm; every Snap bundle URL; and Docker’s Meteor metadata against .meteor/release.

Each mismatch produces a named Actions error and stops the workflow before the bump is pushed or any publishing job starts. Positive coverage runs the verifier against the current checkout, while negative fixtures prove that stale Snap and Meteor values fail the release.

The Unix mirror script used a quoted ~/repos/wekan path, whose tilde could not expand, and kept the entire update workflow inside the condition that created .tools; after the directory existed, later runs did nothing. It now derives the active checkout from the script location, working at ~/repos/wekan on Linux and ~/Documents/repos/wekan on macOS, and always keeps the GitLab and Codeberg mirror clones below that checkout’s ignored .tools directory. Existing clones are updated on every run, and a missing upstream remote is added safely.

The matching Windows batch script uses %USERPROFILE%\Downloads\repos\wekan\.tools, checks every Git operation and performs the same clone, pull, upstream fetch, merge and push sequence. Non-network regression coverage pins all three checkout roots, both mirror destinations, repeat-run updates and the absence of the quoted-tilde fault. These remain human-run publishing scripts; the tests inspect them without contacting a remote.