Skip to content

chore(release): 1.0.1#26

Merged
hoangsonww merged 1 commit intomasterfrom
release/1.0.1
Apr 29, 2026
Merged

chore(release): 1.0.1#26
hoangsonww merged 1 commit intomasterfrom
release/1.0.1

Conversation

@hoangsonww
Copy link
Copy Markdown
Owner

This pull request publishes version 1.0.1 of Forge. It introduces the MCP server feature, allowing Forge to be used as an MCP server for integration with clients like Claude Desktop, Cursor, and Continue, and fixes a release workflow issue affecting Windows artifacts. Documentation and release notes have been updated to reflect these changes.

New features:

  • Added the MCP server surface with the forge mcp serve subcommand, supporting two trust tiers and enabling external MCP clients to plan and run Forge tasks. [1] [2]
  • Documented MCP server usage and per-client setup in docs/MCP-SERVER.md.

Bug fixes:

  • Fixed the release workflow for Windows by forcing shell: bash in install steps, resolving failures due to shell syntax incompatibilities. [1] [2]

Release and versioning:

  • Bumped the package version to 1.0.1 in package.json and updated installation instructions and Docker tags in RELEASES.md. [1] [2]
  • Added detailed release notes for v1.0.1 in CHANGELOG.md and RELEASES.md. [1] [2]

@hoangsonww hoangsonww self-assigned this Apr 29, 2026
@hoangsonww hoangsonww added the bug Something isn't working label Apr 29, 2026
@hoangsonww hoangsonww added documentation Improvements or additions to documentation enhancement New feature or request good first issue Good for newcomers feature Feature request labels Apr 29, 2026
@hoangsonww hoangsonww merged commit d3a046b into master Apr 29, 2026
24 of 34 checks passed
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the project version to 1.0.1, introduces the Forge MCP server feature, and fixes a CI issue affecting Windows artifacts in the release workflow. Feedback indicates that because a new feature is being introduced, the version should be bumped to 1.1.0 (MINOR) rather than 1.0.1 (PATCH) to comply with SemVer policies. Additionally, the rollback documentation in RELEASES.md should be corrected to point to the previous stable version (1.0.0) instead of the current release version.

Comment thread RELEASES.md
Comment on lines +446 to +449
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
Copy link
Copy Markdown
Contributor

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

Comment thread package.json
{
"name": "@hoangsonw/forge",
"version": "1.0.0",
"version": "1.0.1",
Copy link
Copy Markdown
Contributor

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",

Comment thread CHANGELOG.md

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

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

Comment thread RELEASES.md
<!-- Newest at the top. Keep the template from
"Release-notes template" above. -->

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working documentation Improvements or additions to documentation enhancement New feature or request feature Feature request good first issue Good for newcomers

Development

Successfully merging this pull request may close these issues.

1 participant