chore(release): 1.1.0 - #109
Merged
Merged
Conversation
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.
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.
Version bump for the 1.1.0 release.
Both version sites move together —
package.jsonandsrc/utils/version.ts. They are gatedagainst each other:
test/neo4j-schema.test.ts:125asserts the emittedanalyzer_versionequalspkg.version, and that value comes fromANALYZER_VERSION. Break-checked — reverting either onealone fails that test.
ANALYZER_VERSIONis also the cache-invalidation key (src/utils/cache.ts:23), which is why thebump is load-bearing rather than bookkeeping: 1.1.0 changes the cached tree shape (
config_accessesbecame 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
--backendflag and the@cs-au-dk/jellydependency are gone (Replace Jelly with a per-callable defuse linker (tsc + defuse call graph) #98)artifacts/dependencies/unresolved_imports/ config keys (Repository-artifact layer: artifacts, dependencies, config keys (python parity) #101)and
allowJsis forced on so discovered.jsfiles resolveVerification
226 pass / 6 skip / 0 fail; typecheck, build,
gen:schemaandgen:readmeall clean.