Confusing "version" after update - also posted in Discord

[zbruhnke]

Hi folks, quick heads-up from debugging a pin update.

I confirmed the recent pin commit did update nix/sources/openclaw-source.nix correctly (rev/hash/pnpmDepsHash) and regenerated nix/generated/openclaw-config-options.nix, so Git state looks good.

Where I got tripped up was: seeing openclaw-gateway-2026.1.8-2 and openclaw --version made it look like it was still old, but those don’t seem like reliable signals for “which commit is running,” since the gateway package version is hardcoded here:

nix-openclaw/nix/packages/openclaw-gateway.nix

Lines 40 to 42 in ed48468

	stdenv.mkDerivation (finalAttrs: {
	pname = "openclaw-gateway";
	version = "2026.1.8-2";

Curious if it would make sense to add a short post-pin rollout verification step in docs/automation (confirm active /nix/store target changed) so this is easier to validate operationally.

I actually opened a very incorrect issue earlier on the github repo because I got confused by what it was doing, but I deleted and closed it - apologies for that!