Skip to content

chore: bump Tor to 0.4.9.13; 0.4.9.12:6 → 0.4.9.13:0 - #40

Merged
MattDHill merged 1 commit into
masterfrom
next
Sep 24, 2026
Merged

MattDHill merged 1 commit into
masterfrom
next

Conversation

@helix-a

@helix-a helix-a commented Sep 24, 2026

Copy link
Copy Markdown
Member

Summary

  • Patch update to Tor 0.4.9.13; Alpine 3.23 community now supplies tor 0.4.9.13-r0 for x86_64, aarch64, and riscv64, so no Dockerfile change is needed.
  • Set the StartOS version to 0.4.9.13:0 and update localized release notes. No SDK or git dependencies needed updating.

Testing

  • npm run check passed. No package was built, installed, or run in this cycle.
  • On an existing Tor install, upgrade to 0.4.9.13:0, start Tor, and check that it bootstraps, SOCKS requests succeed, and existing onion addresses still answer.

Merge with a merge commit — do not squash. next is long-lived: a merge commit leaves it a true ancestor of master, so it fast-forwards cleanly afterwards. A squash re-lands the same content under a new commit, so the branch is left carrying history master will never contain.

Helix-Harness: pi
Helix-Model: openai-codex/gpt-6-sol
@MattDHill
MattDHill merged commit cf62830 into master Sep 24, 2026
4 checks passed
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