chore(release): 1.2.0 - #147
Merged
Merged
Conversation
ANALYZER_VERSION moves with package.json because it is the cache-invalidation key (utils/cache.ts): this release changes artifact text capture (#117) and per-module id namespacing (#115), so a warm 1.1.0 cache must not be reused against it. Neo4j schema contract is 2.0.0 as of #144 — collapsed back from 2.1.0, since intermediate 2.x versions are not meaningful until every analyzer re-baselines together. Released as a MINOR despite three breaking-marked commits (#115, #117, #144), by explicit decision. The release notes lead with those breaks and their migrations.
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
1 participant
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.
Bumps
package.jsonandANALYZER_VERSIONto 1.2.0, in lockstep (the release workflow fails fast on a mismatch, and the version tests enforce it).ANALYZER_VERSIONis the cache-invalidation key, so a warm 1.1.0 cache is not reused against this tree — #117 changed artifact text capture and #115 changed per-module id namespacing.Breaking, shipped as a minor by explicit decision
Three commits since v1.1.0 are marked
!. Tagging 1.2.0 rather than 2.0.0 means consumers on^1.1.0pick these up automatically, so the release notes lead with them:.js/.jsx/.mjs/.cjsmodules now getcan://javascript/...ids instead ofcan://typescript/.... Anything keying on a JS file's id must re-read it.--eager. Artifact text is now captured whole.schema_versionreports2.0.0, not2.1.0. A database written by a 2.1.0 build repopulates via one full upsert on the next push.Verification
bun test— 239 pass, 0 fail (the two version-lockstep tests confirm the bump is consistent)bun run typecheckclean