Skip to content

v0.6.6

Choose a tag to compare

View all tags
@github-actions github-actions released this 12 Oct 14:07
v0.6.6
04640f5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Dockpipe v0.6.6

Visit dockpipe.com for the Dockpipe website.

The 0.6.x release brings Dockpipe's workflow tools together in a desktop launcher
and a standalone CLI. Run your own project commands, add reusable workflows from
the Marketplace, select secret environments and try running selected work on
another machine. You can use the installed application without a Dockpipe source
checkout or Go compiler.

What's new

A desktop workspace for your workflows

The launcher brings Apps, Workflows, Machines and Activity into one
window. Save project contexts, choose a workflow and execution machine, start or
stop runs, and inspect progress and logs. The same workflows remain available from
the CLI for terminals, servers and CI.

Desktop installers include the launcher and matching CLI. Choose a CLI-only
installation when you do not need the desktop app.

Install the tools you need from the Marketplace

Open Packages → Marketplace to browse optional workflows and tool integrations.
Inspect their platform and dependencies, then install selected packages into your
user store. Downloads are checked against the catalog checksum. The Installed
view shows both user-installed and installer-managed packages.

Base installations include required core. Optional packages, their external tools
and provider sign-ins are separate. Removing an optional user package preserves its
data and settings. See using packages.

Create and reuse your own workflows

Use dockpipe init hello to create a workflow in your project, validate its YAML
before running it, and combine host commands, container steps and packaged
workflows. Host workflows can run without Docker when container preflight is
disabled; container workflows need a reachable engine.

Workflow outputs and reusable container image artifacts help connect steps and
avoid unnecessary image rebuilds. The first-workflow guide
starts with a small host command, then adds a container.

Select a secret environment for each run

Named environments bind selected secret values to workflow environment variables.
Adapters are available for 1Password Environments, AWS Secrets Manager,
Azure Key Vault and Infisical. Select a configured environment with
--secret-environment NAME; configuration stores references rather than secret
values. Existing 1Password vault templates remain supported.

Install and authenticate the matching provider CLI first. The 1Password adapter
requires an op build with op run --environment; AWS bindings currently require
string fields in a JSON secret. See secret environments
for setup and provider limits.

Remote workflow delivery — preview

Pair a worker using a verification code and explicit approval, without transferring
an invitation file or opening inbound SSH on the worker. Preview the selected
workflow sources, assets and package dependencies before submission, then inspect
job results and cancellation through the CLI or launcher.

Remote setup currently targets Linux and macOS. The Cloudflare Tunnel resolver
uses your own Cloudflare account and managed domain; workers connect outbound.
Use the same updated CLI on the broker and worker. Windows workers, a hosted
Dockpipe Cloud service and complete native Mac pairing/sleep-wake qualification
are not included in this release's verified remote experience. Start with
remote setup and limits.

Reusable AI workflows and persistent package data

Optional AI packages let you choose a provider, supply repeatable inputs and inspect
outputs. DorkPipe workflows can add task orchestration, model policies and review
steps. Provider accounts, authentication and any model charges remain separate;
available approval and isolation controls depend on the selected workflow and
runtime. See AI workflows.

Durable package settings and continuity data are separated from disposable project
builds and caches. dockpipe clean --dry-run previews the project files that ordinary
clean would remove; durable package state stays outside that cleanup.

Install

Choose the release asset for your OS and CPU. Native downloads cover Linux amd64
and arm64, macOS Intel and Apple Silicon, and Windows x64. Package availability
does not imply that every distribution, provider or workflow has been qualified.

Native host steps need Bash; Git for Windows provides it on Windows. Docker
is needed for container workflows, not the host-only example below. Provider
CLIs and Git are needed by workflows that use them.

Linux

The installer selects a native CLI package for supported package-manager families,
or a portable archive, and verifies its downloads against the release checksums:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.6/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.6 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

For the desktop on Ubuntu 22.04 / 24.04 or Pop!_OS 22.04, download the matching
CLI and desktop DEBs from this release, verify them against SHA256SUMS.txt, then
install both:

sudo apt install ./dockpipe_0.6.6_amd64.deb ./dockpipe-desktop_0.6.6_amd64.deb

Use arm64 filenames on ARM64. Open Dockpipe from the application menu.
RPM, APK and Arch packages are CLI-only. The same desktop DEBs are installation-tested
on Ubuntu 22.04 and 24.04; that does not establish every downstream desktop setup.

macOS

Install the CLI for Intel or Apple Silicon:

curl -fsSL https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.6/install.sh -o /tmp/dockpipe-install.sh
DOCKPIPE_VERSION=0.6.6 sh /tmp/dockpipe-install.sh
export PATH="$HOME/.local/bin:$PATH"

Desktop artifacts are named dockpipe-desktop_0.6.6_darwin_arm64.dmg for Apple
Silicon and dockpipe-desktop_0.6.6_darwin_amd64.dmg for Intel, and require macOS 13
or newer. They contain Install Dockpipe.pkg for the app and CLI together.
Current desktop packaging is not Developer ID signed and notarized, so Gatekeeper
may block installation. Do not disable macOS security protections to install it.
Use one installation method; the DMG installer refuses an existing foreign CLI or app.

Windows

Download and run the installer in PowerShell:

$installer = Join-Path $env:TEMP 'dockpipe-install.ps1'
Invoke-WebRequest https://github.com/Dockpipe-Industries/dockpipe/releases/download/v0.6.6/install.ps1 -OutFile $installer
& $installer -Version 0.6.6 -SkipWSLSetup

The script verifies checksums and prefers the MSI when it is attached, with a
CLI-only ZIP fallback. The MSI includes the launcher by default; its interactive
installer lets you deselect that feature. Open a new terminal after installation.
WSL is optional and the command above skips its setup. Windows Authenticode signing
is not yet part of the release packaging.

Staging channels and Flatpak

The installation guide
also documents the signed staging APT repository, staging Homebrew formula
and cask, and the Linux amd64 Flatpak preview. These are separate staging
choices; do not mix staging and production APT sources.

The Flatpak contains the launcher, CLI and core, requires KDE Platform 6.10, and
uses a matching Marketplace catalog. Get it from the staging package host using
the guide; do not assume it is attached to this GitHub release or listed on Flathub.
App updates require downloading and verifying a newer bundle. There is no ARM64
Flatpak catalog, and full Bazzite/Podman/SELinux qualification remains outstanding.

Try your first workflow

In a folder you own, run dockpipe init hello, then replace
workflows/hello/config.yml with:

name: hello
docker_preflight: false
steps:
  - id: greet
    kind: host
    cmd: printf 'Hello from Dockpipe!\n'

Validate and run it:

dockpipe --version
dockpipe workflow validate workflows/hello/config.yml
dockpipe --workflow hello --

This prints Hello from Dockpipe! and needs no container engine. For Flatpak,
replace dockpipe with flatpak run --command=dockpipe com.dockpipe.Dockpipe.

Upgrading and known limits

  • Moving from 0.5.x: install the matching native application and core, then
    review the workflow guide
    and install the optional packages your workflows use. --workflow selects a
    workflow; --template remains a compatibility alias for the low-level image
    override and is not an interchangeable workflow selector.
  • Existing package data: keep legacy data until its migration has succeeded.
    Inspect dockpipe clean --dry-run before cleanup: ordinary clean removes the
    entire disposable bin/.dockpipe/ tree. Back up project and package data before
    upgrading; do not assume everything inside an older generated directory is
    expendable.
  • Remote provider name: new Cloudflare setup uses
    dockpipe.cloudflare.remote-edge. Existing cloudflare resolver installations
    are not renamed automatically. Install the new resolver before using new setup
    instructions.
  • Channels and dependencies: staging installation does not change saved package
    remotes automatically. Check Settings → Package Remotes. Optional package
    dependencies, external tools and provider authentication are separate setup steps.
  • Isolation: host commands execute with the permissions of their runtime.
    AI access declarations are not a complete operating-system sandbox, and an
    arbitrary command does not automatically gain a human approval gate.
  • PipeLang: optional typed workflow configuration remains available. The broader
    language/compiler program is experimental; these notes do not promise a
    production-ready general-purpose language, self-hosting compiler or application
    generator.

See the CLI reference
for commands, or report a problem
with your Dockpipe version, platform and steps to reproduce it.

Assets 35
Loading