Submitting new release to Community Registry (v0.3.5)?

Hey, I’m sorry if I’ve overlooked documentation, but I am looking to understand the process for getting new versions of existing services updated to the latest. My service is now at v0.8.8 (with v0.9.1 soon to follow) but the registry lists v0.8.6. I don’t want to spam or bother the team if an automated process exists. Thanks.

The topic here mentions version 0.3.5. Going forward, Start9 is focused on 0.4.0 and, in general, is not updating anything for 0.3.5 services. I know exceptions have been made in the past for key security issues and things like that. If you have updated your service to a new version. Please work on having the packaging for that service updated to 040. See packaging instructions here: Service Packaging - Service Packaging

To request community registry submissions, you should email to: submissions@start9.com with the link to your repo on github

thanks for the reply! i guess ill make sure its “final” when i send an email for v0.3.5.

i put together what i think is a pretty complete tailscale package with some features and ux that improve on the one currently in GitHub - Start9-Community/tailscale-startos: StartOS package for Tailscale · GitHub

ill see if i can collab with the maintainer to make things easier

1 Like