Skip to content

chore(release): signed Scallion native/OpenVPN client interfaces v0.3.78 - #392

Open
ralyodio wants to merge 8 commits into
masterfrom
release/scallion-client-modes-v0.3.78
Open

ralyodio wants to merge 8 commits into
masterfrom
release/scallion-client-modes-v0.3.78

Conversation

@ralyodio

Copy link
Copy Markdown
Collaborator

Purpose

Release the already merged and green Scallion native/OpenVPN client mode interface milestone (#390) as signed v0.3.78 artifacts. The previous signed v0.3.77 release was tagged before #390 was merged, so its installers do not contain c0mpute scallion modes, c0mpute scallion doctor or the guarded .ovpn profile-construction primitive.

Version bump

Synchronizes v0.3.78 in Cargo workspace package versions, Cargo.lock, root/app/package JS manifests, plugin module.toml wrappers, and the web update-feed fallback.

One-shot, guarded signed release

The marker .github/release-signals/scallion-v0.3.78.md triggers .github/workflows/scallion-client-modes-release.yml on merge to master. It:

  1. Verifies the exact Rust version and that both scallion_clients and the Cmd::Scallion CLI are present. Refuses to overwrite an existing tag.
  2. Loads the pinned Rust toolchain, verifies cargo metadata --locked, runs cargo test -p c0mpute-net --locked and cargo test -p c0mpute-cli --locked scallion_cli.
  3. Refuses to release if the latest public tag is not v0.3.77.
  4. Tags the tested master commit v0.3.78 and explicitly dispatches the existing five-platform release.yml (necessary because GitHub's GITHUB_TOKEN tag pushes do not trigger tag-push workflows).
  5. Defers publication to the existing release workflow's five successful cross-platform builds, required SHA256 checksums, minisign signatures, desktop packaging, and verification.

Do not merge until Rust/security CI for this PR is green. A successful merge starts the release gate but does not guarantee it will finish.

Privacy and availability boundaries

This release includes user-facing diagnostics and the dual-client protocol configuration contract. Neither native Scallion TUN, OpenVPN entry server, nor encrypted multihop forwarding is implemented or deployable as a VPN. Both modes correctly report NOT READY. See #386 and #389 for the actual audited transport and gateway work.

Production deployment to dev2 is separately blocked by unreachable TCP/22 from GitHub Actions, tracked as #391. A signed GitHub release does not prove that c0mpute.com updated.

Prior milestone

@github-actions

Copy link
Copy Markdown

ThreatCrush Security Scan

14 finding(s)

HIGH/CRITICAL: 2 | MEDIUM: 8 | LOW: 4

Severity Rule Location
HIGH js-ssrf-outbound-request apps/web/public/sw.js:24
HIGH sh-remote-script-execution scripts/install.sh:611
MEDIUM js-unescaped-html-sink apps/web/src/app/blog/[slug]/page.tsx:53
MEDIUM js-unescaped-html-sink apps/web/src/app/layout.tsx:109
MEDIUM sql-template-interpolation apps/web/src/lib/chat/convo-store.ts:116
MEDIUM sql-template-interpolation apps/web/src/lib/chat/convo-store.ts:117
MEDIUM sql-template-interpolation apps/web/src/lib/chat/push.ts:476
MEDIUM js-dynamic-code-execution apps/web/src/lib/router/verify.ts:91
MEDIUM sh-remote-script-execution scripts/dev-setup.sh:25
MEDIUM sh-eval-expansion scripts/dev-setup.sh:35
LOW py-ssrf-outbound-request examples/business-strategist-agent/chat.py:37
LOW py-ssrf-outbound-request examples/business-strategist-agent/train.py:54
LOW secret-generic-credential node/crates/c0mpute-core/src/webhook.rs:1171
LOW py-path-traversal node/crates/c0mpute-core/tests/fixtures/fake-infernet-text:29

Snippets are redacted; ThreatCrush never prints matched credential material.

This branch has not been deployed

No deployments
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.

1 participant