Skip to content

Conversation

@CosmicToast
Copy link
Contributor

Testing the changes

  • I tested the changes in this PR: YES

Local build testing

  • I built this PR locally for these architectures (if supported. mark crossbuilds):
    • x86_64-musl
    • aarch64-musl (cross)

@classabbyamp
Copy link
Member

this is not a release announced on https://tailscale.com/changelog or https://pkgs.tailscale.com/stable

@CosmicToast
Copy link
Contributor Author

CosmicToast commented Jan 22, 2026

It was tagged here: https://github.com/tailscale/tailscale/releases/tag/v1.94.0 (though now that I look there's also 1.94.1 available). My understanding is that the stable track for them essentially just means waiting for a bit before promoting a version, development stays linear.

Are "promised-stable"-only packages a policy? I didn't spot it in CONTRIBUTING.md or Manual.md (please let me know if I just missed it, else it might make sense to note it :) - I will remember this being the case either way)

@classabbyamp
Copy link
Member

1.94.0 and 1.94.1 are listed as release candidates (in https://pkgs.tailscale.com/release-candidate/)

from CONTRIBUTING.md:

Software need to be used in version announced by authors as ready to use by the general public - usually called releases. Betas, arbitrary VCS revisions, templates using tip of development branch taken at build time and releases created by the package maintainer won't be accepted.

betas includes release candidates

aside from that, as package maintainer of tailscale I only want to package what tailscale themselves consider stable.

@CosmicToast
Copy link
Contributor Author

Thanks! I had indeed missed it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants