nixos/headscale: `ephemeral_node_inactivity_timeout` is deprecated
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- operating-systems
Research direction
Locate the NixOS headscale module and inspect how it renders the ephemeral node inactivity setting. Compare it with headscale's v0.29.0 configuration references [1,2], then verify that the generated configuration uses node.ephemeral.inactivity_timeout and no longer emits the deprecation warning.
Written by the indexing model from the issue text.
Description
Since v0.29.0 the ephemeral_node_inactivity_timeout option is deprecated in favor of node.ephemeral.inactivity_timeout [1,2].
Using any version greater than v0.29.0 with the existing headscale module will emit this warning in journal:
# journalctl -u headscale
...
Jul 02 05:25:54 ... headscale-start[6653]: 2026-07-02T05:25:54Z WRN
Jul 02 05:25:54 ... headscale-start[6653]: WARN: The "ephemeral_node_inactivity_timeout" configuration key is deprecated. Please use "node.ephemeral.inactivity_timeout" instead. "ephemeral_node_inactivity_timeout" has been removed.
...
Additionally, it can prevent headscale from starting up if new configuration is not set [3]. It will only emit warning at this time [4].
related: #534721
cc: @kradalby @Misterio77
- [1] https://github.com/juanfont/headscale/blob/b0c221f3a167505f4337522ba16958701283f69d/CHANGELOG.md?plain=1#L299
- [2] https://github.com/juanfont/headscale/blob/b0c221f3a167505f4337522ba16958701283f69d/hscontrol/types/config.go#L472-L495
- [3] https://github.com/juanfont/headscale/blob/b0c221f3a167505f4337522ba16958701283f69d/hscontrol/types/config.go#L1409-L1411
- [4] https://github.com/juanfont/headscale/blob/b0c221f3a167505f4337522ba16958701283f69d/hscontrol/types/config.go#L556
- Dominant language
- Nix
- Stars
- 26.2k
- Forks
- 20.1k
- Avg merge
- 14h 6m
- Merged PRs (30d)
- 584
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NixOS/nixpkgs
-
1.severity: security
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
0.kind: build failure
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
0.kind: bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
0.kind: enhancement 9.needs: package (update)
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
0.kind: build failure
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
type:content-error
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
stephrobert/blog-roadmap#15 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/windows-rs#4979 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100