openclaw/nix-openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/nix-openclaw.git synced 2026-07-24 21:25:23 -04:00
Code Issues 31 Packages Projects Releases Wiki Activity

Confusing "version" after update - also posted in Discord #31

New Issue
Open
opened 2026-02-15 17:04:37 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 17:04:37 -05:00
Owner
Copy Link
Copy Source

Originally created by @zbruhnke on GitHub (Feb 13, 2026).

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:

https://github.com/openclaw/nix-openclaw/blob/ed48468088dd0652b828417b89e4c4c650b29b6a/nix/packages/openclaw-gateway.nix#L40-L42

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!

Originally created by @zbruhnke on GitHub (Feb 13, 2026). 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: https://github.com/openclaw/nix-openclaw/blob/ed48468088dd0652b828417b89e4c4c650b29b6a/nix/packages/openclaw-gateway.nix#L40-L42 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!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
maintainer-roadmap
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: openclaw/nix-openclaw#31
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?