chore: release v2.4.1#2
Merged
Merged
Conversation
…sts, README guard, lint hardening)
There was a problem hiding this comment.
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.jsonversion to2.4.1. - Bump
forgekit.jsonversion to2.4.1. - Update
CHANGELOG.mdheader from2.4.xto2.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.
| 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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 onmain.This PR exists because direct push to
mainis protected — the v2.4.1 version bump (forgekit.json, package.json, CHANGELOG header) needs to land onmainso the v2.4.1 tag can point at a commit where both manifests read2.4.1.Why a new release
Tag
v2.4.0currently points at commit8277bd1(Phase 3), where:forgekit.jsonstill says"version": "2.0.0"(drift)forgekit.json.instructions[]is missingskills/coding-level/SKILL.mdEnd users of
lgmmo-forgekit-installer@2.4.0would receive a staleforgekit.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.jsonversion: 2.4.0→2.4.1package.jsonversion: 2.4.0→2.4.1CHANGELOG.md[2.4.x]→[2.4.1]Test plan
npm test— 7 + 1 + 3 + 13 = 24 passnpm run lint— passes (4 expected legacy-skill allowlist warnings)v2.4.1at the merge commit and push to triggerrelease.ymlSection 0 — Non-negotiable Principles Compliance
:ck:autoGenerated by Claude Code