Skip to content

Releases: junited31/dotunnel

dotunnel 0.1.6

Choose a tag to compare

@github-actions github-actions released this 09 Oct 03:53
f3b8869

dotunnel 0.1.6

Integrated permission setup: review workspace file read/write rules, optional fixed CLI jobs and live-agent action grants before credentials or persistent artifacts. New grants default empty; final approval defaults No. Runtime scope approvals and native agent confirmations remain separate.

Upgrade boundary: existing configs without file_access are rejected by 0.1.6. Package installation does not migrate them. Keep a private backup, stop owned clients, explicitly review/migrate file rules and supervision project/profile actions, validate, then restart. Preserve existing credentials/profile/state; setup does not silently recreate damaged authority. See the bilingual guide in the repository.

Live profiles default to the documented compatible executable-leaf policy, which deliberately permits writable/shared-inode executable code; strict remains available. This is not a native-agent sandbox or an authentication guarantee. Existing installed CLIs are not changed by setup.

Provenance and verification

  • Source/tag commit: f3b8869a13038fe09d3920a6e66d976a26189227.
  • PR #8 actual web PASS, after two verified correction rounds.
  • Exact merged-main CI: Secret scan, Python 3.11, Python 3.13 PASS.
  • Draft preparation: source validation, universal wheel, release-specific installer and four assets PASS.
  • All four downloaded assets independently checked against GitHub digests; wheel/installer also match release-manifest.json and SHA256SUMS.
  • Wheel: dotunnel-0.1.6-py3-none-any.whl, 142242 bytes, SHA-256 17f5c95c215f29028bf9a7ce8b563a8bf5e013437b55c61179d5952979f79de1.

The attached install.sh is pinned specifically to this release. Repository-main stable installer and bilingual manual-install pins advance in a separate reviewed PR; no release asset is overwritten.

Verification used synthetic fixtures and source/CLI/MCP boundaries. No real provider/native-agent execution or production deployment is established by these release checks.

dotunnel 0.1.5

Choose a tag to compare

@github-actions github-actions released this 08 Oct 00:41
07dc43f

dotunnel 0.1.5

Changes

  • Optional core Herdr/tmux supervision from explicitly configured project/profile/connection registries. The seven base MCP tools remain unchanged; enabling supervision adds one shared set of eight agent_* tools. No broadcast or automatic fallback.
  • Explicit owner-only supervision state initialization/reinitialization, scoped approvals, identity-bound observations and operation receipts. Unknown outcomes require reconciliation rather than blind retry; arbitrary existing tmux panes remain read-only.
  • Hardened state rotation, atomic persistence, bounded status output and CLI process-group cleanup. Separately detached backend agents are not terminated by CLI helper cleanup.
  • Separately installed dotunnel-adapter-runner with fixed registry profiles, local consent and durable replay/ownership. It is distinct from core supervision; it ships no backend/provider adapters and does not provide Orca support.
  • Package metadata and public module version both identify 0.1.5.

Assets and verification

Source: 07dc43f763fac287be49b4a2511e79fcf85a71d2 (PR #6). The reviewed head and merged source have identical Git trees.

  • Exact-source main CI: Secret scan and Python 3.11/3.13 succeeded.
  • Stable-tag draft preparation: source/main-CI validation, wheel preparation and draft attachment succeeded.
  • All four downloaded draft assets match the prior verified dry-run byte-for-byte. The wheel's 24 Python source files match the reviewed source.
Asset Bytes SHA-256
dotunnel-0.1.5-py3-none-any.whl 123908 5b617552d1d9dbaabd4209a99f42c4a25e7757fad8c3e9a0e684d9f01a949810
install.sh 8880 e3014b6c635d4af73e0121645d450fd1035d225e743c8d1fbd7a7372efe677ee

SHA256SUMS and release-manifest.json are included. The release-specific installer pins this wheel's exact size and checksum. The repository's default installer now pins the same published 0.1.5 wheel through the separately reviewed PR #7, merged as 70f12f08be9f6636221d7b2ba4560ab17b21263a. Merged-main CI succeeded; the merged installer is byte-identical to the Release asset.

Publication does not install or activate supervision, restart services, alter configuration/credentials, or run provider/native-agent tasks. Supervision requires explicit configuration and initialization; backend observations or input delivery do not prove logical task success. Live provider/native-agent execution verification remains deferred.

dotunnel 0.1.4

Choose a tag to compare

@junited31 junited31 released this 06 Oct 08:38

Anonymous HTTPS updates without GitHub CLI or login; existing wheel size, SHA-256, identity and interactive approval checks remain. Public CI scans Git history, runs Python 3.11/3.13 tests, builds wheels and checks installed CLIs with read-only permissions. Includes the checksum-pinned one-line installer and staged Gitleaks guard. Existing running services and credentials are not changed. Pre-0.1.4 installations must use their old updater once or manually install the verified wheel to obtain the new updater. Wheel: 80847 bytes; SHA-256 6ed19be1672ac3961f0e8230abd43af47c08eee4720ad2898b21d3ee6fc1af0f.

dotunnel 0.1.3

Choose a tag to compare

@junited31 junited31 released this 06 Oct 05:21

Pre-publication security fixes: trusted absolute sudo/package-manager execution, terminal-only existing setup, isolated Python module launch, and Claude token file boundary correction. Check wheel SHA-256 before installation: fbb6fd8d2ebea7368fe86e5096fe40c1830d829065c81ca3e7ed49e552eb9912. Existing 0.1.0–0.1.2 profiles are not rewritten by updates: insert -I between the absolute Python interpreter and -m dotunnel before the next connection start, preserving all paths, Tunnel ID and key references. See CHANGELOG and both READMEs. No services or credentials are changed automatically.

dotunnel 0.1.2

Choose a tag to compare

@junited31 junited31 released this 06 Oct 03:34
  • If Bubblewrap is missing and the setup account can use sudo, setup offers to install it ([Y/n], Enter approves) with the distribution's command, then re-checks and continues to CLI selection. Without sudo, or after a declined/failed install, it shows the command for an administrator.
  • Install commands are non-interactive (apt-get -y, dnf -y, pacman --noconfirm, zypper --non-interactive, apk add).
  • Prefer a runtime account without sudo; tasks and CLI jobs inherit its permissions.

Wheel SHA-256: 8350769c1790549c540f0efe6772fd7f064de93bea621b5919c1fbd7d383ad9c

dotunnel 0.1.1

Choose a tag to compare

@junited31 junited31 released this 06 Oct 03:15
  • setup checks Bubblewrap (presence and a real isolation probe) before optional CLI integrations and shows the distribution's sudo install command; Enter re-checks, s skips. dotunnel never runs sudo.
  • doctor reports the same Bubblewrap status.
  • Bubblewrap remains required only for optional Codex/Claude Code/OMP integrations.

Wheel SHA-256: 121342c80d2aa2a62e0ea4fe0210b46f6d3f0b0c514dbcd82da1429a672cf27b

dotunnel 0.1.0

Choose a tag to compare

@junited31 junited31 released this 06 Oct 02:56

First release. Install with the instructions in README.md / README.ko.md, then use dotunnel update for later versions.

Wheel SHA-256: 07ed434ffc353440b88269ffd341ff0dd2a410291abcee92ef6f78a0dc82be14