Track creation guardrail request for the "headscale" snap

store-requests guardrail
1

Hi store team,

I’d like to request a track creation guardrail for the Headscale snap, so that new minor-version tracks can be created automatically by our CI using create-tracks API rather than through a forum request each time (ref).

  • Snap: headscale
    • Snap ID: CERKCHBF9chC90ufXJHcDWyEztP3Qfl0
    • Contact: `solutions-engineering@lists.canonical.com`
    • Requested track pattern: ^\d+\.\d+$ (anchored - e.g. 0.28, 0.29, 1.0)

Rationale:

Upstream ships breaking changes across minor versions (which is the reason for previous manual requests). That means users need to pin a minor line and stay on it deliberately.

Non-blocking question

I also notice tracks carry a version-pattern field (currently null for all of ours). Is it to constrain which snap versions may be released to a given track? If so is it possible to have that applied to guardrail-created tracks - so that a track X.Y only accepts revisions whose version matches? (e.g. a CI error could not publish a 0.29.x revision onto the 0.27 track)

If that’s possible, we’d very much like it. If it isn’t, or if it needs to be set per track at creation time, the guardrail alone is still fully what we need and we’re good to have just that.

Thanks!

2

For your reference @jneo8 ^

3

Hi,

The Headscale guardrails are now active. You can create numeric track names (e.g., 0.28, 0.29, 1.0) directly via the create-tracks API, making track creation fully self-service. Regarding version patterns: a release will be rejected if a revision does not match the target track’s pattern. Please note that patterns use glob syntax (e.g., 0.28.*) and must be passed during creation: [{‘name’: ‘0.28’, ‘version-pattern’: ‘0.28.*’}]

Thanks, Shweta

1 Like
4

Thank you for the quick response!