Repository navigation
chore(release): 2.3.0 - #60
Closed
Animesh-Sri-bugb wants to merge 1 commit into
Closed
Animesh-Sri-bugb wants to merge 1 commit into
Animesh-Sri-bugb wants to merge 1 commit into
Conversation
Bump the version to 2.3.0, close the Unreleased changelog section as 2.3.0, and regenerate the committed artifacts for the new generator stamp. The annotation_hash is unchanged.
Contributor
Author
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.
Release prep for 2.3.0. No code change; this PR only bumps the version and regenerates the files that record it.
What changed
npm version 2.3.0 --no-git-tag-version: updatespackage.jsonand the two root entries ofpackage-lock.json.src/version.tsreadspackage.json, so that is the whole bump (see CONTRIBUTING.md → Releasing).CHANGELOG.md: theUnreleasedsection becomes[2.3.0] — 2026-10-11(the dashboard redesign, theguardlink pathsno-sink fix, and deterministic parse order), and a new emptyUnreleasedsection sits above it.guardlink artifacts .(run from this branch's build, so it stampsguardlink@2.3.0): updates the%% generator:header in all 53.mmdfiles,provenance.generatorin.guardlink/model.json, and the generator line inMANIFEST.jsonandgraph/README.md.Review notes
annotation_hashis byte-identical before and after:sha256-v3:054099e5…c7528. Only the version moved..guardlink/model.jsonalso carries fourlocation.linechanges: one@flowsinsrc/dashboard/generate.ts(102 → 101) and three annotations insrc/mcp/server.ts(1220–1222 → 1221–1223). These are stale anchors from 44ede95, which shifted those lines without regenerating the artifacts. Line anchors are not part of the hash.Verification
npm ci && npm run build && npm test && npm run lint: 124 test files, 2249 passed, 1 skipped; lint clean.guardlink validate . --artifacts: artifacts are current and drawable.guardlink --version→2.3.0.No tag was created. Publishing happens when the GitHub Release is created (
.github/workflows/release.yml).