Skip to content

Releases: telerik/forge

Release v0.1.3-dev.1

Release v0.1.3-dev.1 Pre-release
Pre-release

Choose a tag to compare

Progress Forge CLI v0.1.3-dev.1

What's Changed

No exact match found, trying base version: 0.1.3

Distribution Assets

Public stable releases are automatically mirrored to telerik/forge.
Tags prefixed with desktop- publish directly to the public repository.
Use the public repository for downloads: https://github.com/telerik/forge/releases

Installation Guide

Pre-release builds are not recommended for production use.

Supported platforms:

  • Linux (x86_64, aarch64) - Binary, Debian package, and RPM package
  • Linux legacy (x86_64, aarch64) - Binary and RPM for glibc 2.28+
  • Windows (x86_64) - Binary
  • macOS (Intel x86_64, Apple Silicon aarch64) - Binary
  • Desktop app - Windows x86_64 (MSI/NSIS), macOS x86_64/aarch64 (DMG), Linux x86_64 (AppImage/Debian)
  • Arch Linux - PKGBUILD package

Verification

Artifacts are signed with platform-native code signing plus detached GPG signatures:

  • Windows (frg-*.exe, install.ps1) - Authenticode signed with the Progress EV code signing certificate.
  • macOS (frg-*-darwin) - signed with a Progress Apple Developer ID Application certificate and notarized by Apple.
  • Desktop installers - Authenticode signed on Windows and Developer ID signed, notarized, and stapled on macOS.
  • All artifacts (binaries, .deb/.rpm/.tar.gz packages, scripts, and SHA256SUMS) additionally carry detached GPG signatures.

To verify GPG signatures:

# Import public key (first time only)
gpg --import public-key.asc

# Verify the clearsigned manifest, then verify its listed payload hashes
gpg --verify SHA256SUMS.asc
sha256sum -c SHA256SUMS

# Verify a detached payload signature
gpg --verify install.sh.asc install.sh

Release v0.1.2

Choose a tag to compare

@telerik-github-automation telerik-github-automation released this 08 Oct 06:43

Progress Forge CLI v0.1.2

What's Changed

Patch release of the 0.1.x line that fixes checksum verification in the
Windows installer.

Fixed

  • installer: install.ps1 no longer fails with "Binary not found in
    checksum file" when verifying a release download. It now accepts the ./
    file name prefix used in the published SHA256SUMS, as install.sh and
    frg update already did

Installation

Quick Install (No Authentication Required)

Linux/macOS:

curl -fsSL https://github.com/telerik/forge/releases/latest/download/install.sh | sh

Windows (PowerShell 6+):

Invoke-WebRequest -Uri 'https://github.com/telerik/forge/releases/latest/download/install.ps1' -OutFile install.ps1
.\install.ps1

Install Specific Version

Linux/macOS:

curl -fsSL https://github.com/telerik/forge/releases/download/v0.1.2/install.sh | sh

Windows:

Invoke-WebRequest -Uri 'https://github.com/telerik/forge/releases/download/v0.1.2/install.ps1' -OutFile install.ps1
.\install.ps1

📦 Full Documentation

Verification

All artifacts are cryptographically signed:

  • Windows - Authenticode signed (Progress EV certificate)
  • macOS - Apple Developer ID signed and notarized
  • All platforms - GPG detached signatures
# Import public key and verify
gpg --import public-key.asc
gpg --verify <artifact>.asc <artifact>

Platform Support

Platform Binary Package
Linux x86_64 frg-0.1.2-x86_64-linux .deb, .rpm
Linux ARM64 frg-0.1.2-aarch64-linux .deb, .rpm
macOS Intel frg-0.1.2-x86_64-darwin -
macOS Apple Silicon frg-0.1.2-aarch64-darwin -
Windows x86_64 frg-0.1.2-x86_64-windows.exe -
Arch Linux progress-forge-0.1.2-arch.tar.gz PKGBUILD

Built with ❤️ by the Progress Forge CLI team

Release v0.1.1

Choose a tag to compare

@telerik-github-automation telerik-github-automation released this 07 Oct 16:37

Progress Forge CLI v0.1.1

What's Changed

Patch release of the 0.1.x line with desktop workflow editing and artifact
approval improvements, unique issue branches, and run cancellation and Windows
fixes.

Added

Workflow Editing and Artifact Approvals in the Desktop App (#1540)

Reviewing the files a run produced and answering its approval gate now happen in
one panel, and workflow edits stay in a draft until they are saved.

Key capabilities:

  • Pending approvals open a side panel listing the files reported by the
    preceding steps, grouped by step and folder; Approve submits the gate's
    required code and the configured or signed-in approver email, and Reject
    asks for confirmation and an optional reason
  • A confirmed rejection shows Rejected on the approval step, the task header,
    and the task list instead of Failed
  • Multi-file Markdown plans open in a read-only panel with a file list; Edit
    opens a reported .md, .txt, .json, .toml, .yaml, or .yml file in
    its associated application, and the preview refreshes after external edits
  • Creating or duplicating a workflow opens an unsaved draft; Save writes the
    complete definition atomically, Save and run opens the launcher after
    saving, and leaving with unsaved edits asks before discarding them
  • Workflow states can be reordered by dragging or with move-up and move-down
    buttons

Changed

  • branch: The default [branch].naming template is now
    forge/issue-{issue}-{slug}-{uid}. The new {uid} token is a short random ID
    fixed per job, so a fresh job for an issue that already has a remote branch no
    longer reuses and collides with it
    (#1550)
  • branch: on_collision = "suffix" appends a short random suffix instead of
    a short commit SHA (#1550)
  • contract: Contract 1.16.0 adds optional warning.approval_rejection
    metadata for confirmed approval rejections, and 1.17.0 adds
    workflow.create_definition for atomically creating a complete workflow
    (#1540)

Fixed

  • engine: Cancelling a run from the desktop app now stops its coding agent
    and the agent's subprocesses instead of letting the agent keep working
    (#1551,
    #1554)
  • engine: On Windows, the desktop app no longer opens visible console windows
    for git, PowerShell, and agent CLI processes it starts during a run
    (#1555)
  • desktop: Workflow steps collapse once they complete, including the final
    step of a finished run (#1550)
  • desktop: Subject labels no longer repeat the issue number, for example
    "Issue #3" instead of "#3 · Issue #3"
    (#1540)

Installation

Quick Install (No Authentication Required)

Linux/macOS:

curl -fsSL https://github.com/telerik/forge/releases/latest/download/install.sh | sh

Windows (PowerShell 6+):

Invoke-WebRequest -Uri 'https://github.com/telerik/forge/releases/latest/download/install.ps1' -OutFile install.ps1
.\install.ps1

Install Specific Version

Linux/macOS:

curl -fsSL https://github.com/telerik/forge/releases/download/v0.1.1/install.sh | sh

Windows:

Invoke-WebRequest -Uri 'https://github.com/telerik/forge/releases/download/v0.1.1/install.ps1' -OutFile install.ps1
.\install.ps1

📦 Full Documentation

Verification

All artifacts are cryptographically signed:

  • Windows - Authenticode signed (Progress EV certificate)
  • macOS - Apple Developer ID signed and notarized
  • All platforms - GPG detached signatures
# Import public key and verify
gpg --import public-key.asc
gpg --verify <artifact>.asc <artifact>

Platform Support

Platform Binary Package
Linux x86_64 frg-0.1.1-x86_64-linux .deb, .rpm
Linux ARM64 frg-0.1.1-aarch64-linux .deb, .rpm
macOS Intel frg-0.1.1-x86_64-darwin -
macOS Apple Silicon frg-0.1.1-aarch64-darwin -
Windows x86_64 frg-0.1.1-x86_64-windows.exe -
Arch Linux progress-forge-0.1.1-arch.tar.gz PKGBUILD

Built with ❤️ by the Progress Forge CLI team

Release v0.1.0

Choose a tag to compare

@telerik-github-automation telerik-github-automation released this 06 Oct 12:20

Progress Forge CLI v0.1.0

First stable release of the public 0.1.x version line, promoting 0.1.0 with desktop workflow-launch and run-control fixes.

Built with ❤️ by the Progress Forge CLI team