Skip to content

chore(release): 1.1.0 - #109

Merged
rahlk merged 1 commit into
mainfrom
chore/release-1.1.0
Aug 31, 2026
Merged

chore(release): 1.1.0#109
rahlk merged 1 commit into
mainfrom
chore/release-1.1.0

Conversation

@rahlk

@rahlk rahlk commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Version bump for the 1.1.0 release.

Both version sites move together — package.json and src/utils/version.ts. They are gated
against each other: test/neo4j-schema.test.ts:125 asserts the emitted analyzer_version equals
pkg.version, and that value comes from ANALYZER_VERSION. Break-checked — reverting either one
alone fails that test.

ANALYZER_VERSION is also the cache-invalidation key (src/utils/cache.ts:23), which is why the
bump is load-bearing rather than bookkeeping: 1.1.0 changes the cached tree shape (config_accesses
became a required field on TSCallable), so a warm 1.0.0 cache must not be reused against it.

The Neo4j schema contract stays at 2.1.0 by decision — it re-baselines once every analyzer's schema
is stable, not once per release.

What 1.1.0 contains

Verification

226 pass / 6 skip / 0 fail; typecheck, build, gen:schema and gen:readme all clean.

ANALYZER_VERSION moves with package.json because it is the cache-invalidation
key (utils/cache.ts:23), and this release changes the cached tree shape --
config_accesses became a required field on TSCallable. A warm 1.0.0 cache must
not be reused against a 1.1.0 tree.

Neo4j schema contract stays 2.1.0: it re-baselines once every analyzer's schema
is stable, not per release.
@rahlk
rahlk merged commit f444e35 into main Aug 31, 2026
1 check passed
@rahlk
rahlk deleted the chore/release-1.1.0 branch August 31, 2026 13:25
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.

1 participant