Skip to content

chore: release v2.4.1#2

Merged
Duy-Nguyen-2006 merged 1 commit into
mainfrom
claude/forgekit-upgrade-plan-ANcrZ
May 9, 2026
Merged

chore: release v2.4.1#2
Duy-Nguyen-2006 merged 1 commit into
mainfrom
claude/forgekit-upgrade-plan-ANcrZ

Conversation

@Duy-Nguyen-2006

Copy link
Copy Markdown
Owner

Summary

Release v2.4.1 bundling the fixes from the verify report into a tagged release. Fixes apply on top of 8aeead4 (verify-report fixes commit) which is already on main.

This PR exists because direct push to main is protected — the v2.4.1 version bump (forgekit.json, package.json, CHANGELOG header) needs to land on main so the v2.4.1 tag can point at a commit where both manifests read 2.4.1.

Why a new release

Tag v2.4.0 currently points at commit 8277bd1 (Phase 3), where:

  • forgekit.json still says "version": "2.0.0" (drift)
  • forgekit.json.instructions[] is missing skills/coding-level/SKILL.md

End users of lgmmo-forgekit-installer@2.4.0 would receive a stale forgekit.json. v2.4.1 ships the corrected manifest plus the verify-report hardening (README guard, routing tests, version sync check, MAX_SKILL_LINES=200 with allowlist).

Changes in this PR

  • forgekit.json version: 2.4.02.4.1
  • package.json version: 2.4.02.4.1
  • CHANGELOG.md [2.4.x][2.4.1]

Test plan

  • npm test — 7 + 1 + 3 + 13 = 24 pass
  • npm run lint — passes (4 expected legacy-skill allowlist warnings)
  • After merge: tag v2.4.1 at the merge commit and push to trigger release.yml

Section 0 — Non-negotiable Principles Compliance

  • §0.1 No new entrypoint outside :ck:auto
  • §0.2 Spec-first / single approval gate unchanged
  • §0.3 No new user choice required
  • §0.4 ForgeCode-native first preserved
  • §0.5 Token efficiency unchanged
  • §0.6 Repo cleanliness unchanged (only 3 small text edits)
  • §0.7 Output convention unchanged

Generated by Claude Code

@Duy-Nguyen-2006 Duy-Nguyen-2006 marked this pull request as ready for review May 9, 2026 15:10
Copilot AI review requested due to automatic review settings May 9, 2026 15:10
@Duy-Nguyen-2006 Duy-Nguyen-2006 merged commit 74915c2 into main May 9, 2026
2 checks passed

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

Prepares the v2.4.1 release commit by bumping version identifiers across the installer package manifest, ForgeKit manifest, and changelog so the v2.4.1 git tag can point at a commit with consistent metadata.

Changes:

  • Bump package.json version to 2.4.1.
  • Bump forgekit.json version to 2.4.1.
  • Update CHANGELOG.md header from 2.4.x to 2.4.1.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File Description
package.json Updates npm package version to 2.4.1 for the release tag.
forgekit.json Updates ForgeKit manifest version to 2.4.1 to keep manifests in sync.
CHANGELOG.md Updates the top release header to 2.4.1.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread CHANGELOG.md
All notable changes to ForgeKit are documented in this file. Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).

## [2.4.x] - 2026-05-09
## [2.4.1] - 2026-05-09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants