Skip to content

chore: release v0.4.0 #91

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
N4M3Z merged 1 commit into from
Jul 13, 2026
Merged

chore: release v0.4.0 #91

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,14 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/).

## [Unreleased]

## [0.4.0] - 2026-07-13

### Added

- The TUI acts, not just displays: deploy-to-target and harness-launch pickers (add targets by path, persisted to `~/.config/forge`), in-panel filtering with `/` and problems-only with `!`, an enterable Overview that jumps to status and kind views, one unified artifact detail with numbered tabs across skills, ADRs, and companions, letter shortcuts for sections, tuicr-style gutter word wrap, diff hunk navigation with per-line commenting, clickable commits, and git plus jj history views. (#89)
- `forge install` and `forge deploy` accept `--only <prefix>` for single-artifact deploys. Matching is boundary-aware and survives provider slugging (gemini's `SecurityArchitect` → `security-architect`); the flag implies no-prune and refuses to operate over a corrupt `.manifest` rather than silently rebuilding a partial one. (#89)
- Provider `defaults.yaml` targets accept per-kind maps alongside single strings, deploying agents, skills, and rules to different roots under one provider. (#86)
- Release tarballs ship with GitHub build provenance attestations. (#84)
- `forge launch <tool>` composes coding-tool launches through ordered middleware (`pxpipe`, `otel`, `presidio`, `squid`, `docker`, `tmux`) plus external `forge-launch-mw-*` script middleware. It supports configured default chains and tool base-url env mappings, `--with a,b,c`, legacy `--pxpipe`/`--direct`, `--tmux[=name]`, scoped child env injection, best-effort proxy preflight, and `--dry-run` plan output.
- The `agentskills` provider installs Agent Skills-compatible `SKILL.md` files under `.agents/skills/<Name>/SKILL.md`, with `agents` as an alias for `--provider agents` and an Agent Skills frontmatter whitelist.
- `forge adopt <url>` fetches an upstream HTTPS artifact (or `file://` fixture), applies the `align` transform into a module skill or companion file, and writes an `adopt/v1` provenance sidecar with the upstream digest pin.
Expand Down
2 changes: 1 addition & 1 deletion Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "forge-cli"
version = "0.3.2"
version = "0.4.0"
edition = "2024"
license = "EUPL-1.2"
repository = "https://github.com/N4M3Z/forge-cli"
Expand Down
2 changes: 1 addition & 1 deletion module.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
name: forge-cli
version: 0.3.2
version: 0.4.0
type: binary
description: "Forge module toolkit — assemble, validate, and deploy skills, agents, and rules across AI coding providers."
events: []