Skip to content

fix(start-os): bundle the tor s9pk from prod, not alpha - #3661

Merged
dr-bonez merged 1 commit into
masterfrom
fix/bundle-tor-from-prod
Aug 12, 2026
Merged

fix(start-os): bundle the tor s9pk from prod, not alpha#3661
dr-bonez merged 1 commit into
masterfrom
fix/bundle-tor-from-prod

Conversation

@MattDHill

Copy link
Copy Markdown
Member

The image build downloads a Tor s9pk to /usr/lib/startos/tor_<arch>.s9pk for the 0.3.5.1 migration to sideload (version/v0_4_0_alpha_20.rs), so it is the Tor a migrating server lands on.

It was pulled from alpha, which every push to tor-startos master publishes to. That put unreleased, untested Tor revisions straight in front of migrating users.

Pull from prod instead.

-start-cli --registry=https://alpha-registry-x.start9.com registry package download tor …
+start-cli --registry=https://registry.start9.com registry package download tor …

No effect today — alpha, beta and prod all currently serve 0.4.9.11:5. Going forward it means a new Tor reaches migrating servers once it is promoted to prod and an image is built after that.

🤖 Generated with Claude Code

The image bundles a tor s9pk for the 0.3.5.1 migration to sideload, so it is
what migrating servers land on. It was pulled from alpha, which every push to
tor-startos master publishes to — untested code, shipped straight to users.
Take it from prod instead.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@dr-bonez
dr-bonez merged commit 5e9c8ef into master Aug 12, 2026
24 checks passed
@dr-bonez
dr-bonez deleted the fix/bundle-tor-from-prod branch August 12, 2026 17:18
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