Skip to content

chore(release): 1.0.1 #26

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
hoangsonww merged 1 commit into from
Apr 29, 2026
Merged

chore(release): 1.0.1 #26

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
10 changes: 10 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,16 @@

All notable changes to Forge are tracked here. Follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).

## [1.0.1] - 2026-04-29
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot Apr 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

As noted in the package.json feedback, this release introduces a new feature and should follow the project's SemVer policy by bumping the MINOR version to 1.1.0.

Suggested change
## [1.0.1] - 2026-04-29
## [1.1.0] - 2026-04-29


Patch release: ships the MCP server surface (`forge mcp serve`) that landed after 1.0.0, plus a CI fix that unblocks the Windows artifacts job in the release workflow.

### Added
- **Forge as an MCP server** (`forge mcp serve`). Exposes the runtime as MCP tools so Claude Desktop, Cursor, Continue, and any other MCP client can plan and run Forge tasks from their own chat. Two trust tiers: read-only (default) exposes `forge_status`, `forge_plan`, `forge_get_task`, `forge_list_tasks`; `--allow-execute` (or `FORGE_MCP_ALLOW_EXECUTE=true`) adds `forge_run` and `forge_cancel_task`. Wraps the same `orchestrateRun()` entry point as the CLI/REPL/dashboard, so MCP-driven plans are byte-identical paths. See `docs/MCP-SERVER.md` for per-client setup.

### Fixed
- **Release workflow Windows artifacts**: the three install steps in `release.yml` used bash-only constructs (`2>/dev/null`, `||`-grouped fallbacks, `rm -rf`) which PowerShell parses as filesystem paths. Force `shell: bash` so the Windows runner uses Git Bash. The artifacts (win32-x64) job no longer crashes with `Could not find a part of the path 'D:\dev\null'`.

## [1.0.0] - 2026-04-27

First stable release. The runtime, agentic loop, persistence model, permission system, sandbox, and provider abstractions are now considered stable surface area. Breaking changes from here on bump MAJOR.
Expand Down
18 changes: 16 additions & 2 deletions RELEASES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -443,10 +443,10 @@ FROM ghcr.io/hoangsonw/forge-agentic-coding-cli:0.2.0

```bash
# npm — downgrade explicitly.
npm install -g @hoangsonw/forge@1.0.0
npm install -g @hoangsonw/forge@1.0.1

# Docker — swap the tag.
docker pull ghcr.io/hoangsonw/forge-agentic-coding-cli:1.0.0
docker pull ghcr.io/hoangsonw/forge-agentic-coding-cli:1.0.1
Comment on lines +446 to +449
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot Apr 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

In the Roll back section, the examples should point to a known stable version (e.g., 1.0.0) rather than the version currently being released (1.0.1). Providing the current version as a rollback target is counter-intuitive as it wouldn't result in a actual downgrade if the current version is what the user is trying to move away from.

Suggested change
npm install -g @hoangsonw/forge@1.0.1
# Docker — swap the tag.
docker pull ghcr.io/hoangsonw/forge-agentic-coding-cli:1.0.0
docker pull ghcr.io/hoangsonw/forge-agentic-coding-cli:1.0.1
npm install -g @hoangsonw/forge@1.0.0
# Docker — swap the tag.
docker pull ghcr.io/hoangsonw/forge-agentic-coding-cli:1.0.0


# Tell the built-in updater to stop nagging about a broken version.
forge update ignore 0.2.0
Expand Down Expand Up @@ -644,6 +644,20 @@ Stable within a MAJOR. Migrations under [`src/migrations/runner.ts`](src/migrati
<!-- Newest at the top. Keep the template from
"Release-notes template" above. -->

### v1.0.1 — 2026-04-29
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot Apr 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Update the version header to v1.1.0 to align with the MINOR version bump required for new features.

Suggested change
### v1.0.1 — 2026-04-29
### v1.1.0 — 2026-04-29


#### Highlights
- **Forge as an MCP server** (`forge mcp serve`) — Claude Desktop, Cursor, Continue, and any MCP client can now plan and run Forge tasks from their own chat. Read-only by default; opt in to execution with `--allow-execute`.
- **Release workflow fix** — Windows artifacts job no longer crashes on `2>/dev/null` because the install steps now run under Git Bash.

#### Added
- `forge mcp serve` subcommand with `--allow-execute` and `--cwd` flags.
- New tools: `forge_status`, `forge_plan`, `forge_get_task`, `forge_list_tasks`, `forge_run`, `forge_cancel_task`.
- `docs/MCP-SERVER.md` with per-client (Claude Desktop, Cursor, plain MCP) setup.

#### Fixed
- `.github/workflows/release.yml` install steps now force `shell: bash` so the Windows runner stops parsing `/dev/null` as a path.

### v1.0.0 — 2026-04-27

#### Highlights
Expand Down
4 changes: 2 additions & 2 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@hoangsonw/forge",
"version": "1.0.0",
"version": "1.0.1",
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot Apr 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

According to the versioning policy defined in RELEASES.md (line 70), a new feature like the MCP server subcommand (forge mcp serve) warrants a MINOR version bump rather than a PATCH bump. Since this is a post-1.0 release where SemVer is strictly enforced (line 73), this version should likely be 1.1.0 instead of 1.0.1.

Suggested change
"version": "1.0.1",
"version": "1.1.0",

"description": "Forge - a local-first, multi-agent, programmable software-engineering runtime",
"license": "MIT",
"author": "Son Nguyen (hoangsonw)",
Expand Down
Loading