Repository navigation
2.2: @ingestron/core, ProjectSnapshot and ingestron@2.2.0 - #33
Merged
Merged
Conversation
added 3 commits
November 9, 2026 04:51
@ingestron/cli exports only the command's own API, and @ingestron/authoring starts from ProjectSnapshot. The site's code imports from @ingestron/core, the CLI reference says where the API now lives, the upgrade guide says what to change, and the versions page lists @ingestron/core. The extension's version is synced to 2.1.4. Signed-off-by: The Architect <hello@ingestron.io>
The pages and CI templates install ingestron@2.2.0. The troubleshooting test reads the writer from @ingestron/generate's dist/apply/ and uses ProjectSnapshot; the CLI reference test expects the cli and core README links. Signed-off-by: The Architect <hello@ingestron.io>
Signed-off-by: The Architect <hello@ingestron.io>
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.
For the 2.2 release:
@ingestron/coreand usesProjectSnapshotfrom@ingestron/authoring.@ingestron/core, and the upgradeguide has "Upgrade to 2.2" with what code that calls the packages changes.
ingestron@2.2.0; the versions pagelists
@ingestron/coreand shows the extension's 2.1.4.Every other page builds the same as on
main.pnpm validatepasses againstthe packages of this release; the lockfile is refreshed once they are
published.
One release across seven repositories
This change ships together with the
refactor/module-layoutpull requests iningestron,pack-databricks,pack-adf,pack-synapse,pack-duckdb,vscodeanddocs. Packages are published before the ones that depend onthem:
@ingestron/config1.6.0,@ingestron/generate1.1.0,@ingestron/definitions1.12.0@ingestron/pack-databricks2.2.0,@ingestron/pack-adf2.2.0,@ingestron/pack-synapse2.1.0,@ingestron/pack-duckdb2.1.0@ingestron/core1.0.0@ingestron/authoring2.2.0@ingestron/cli2.2.0 andingestron2.2.0The
vscodeanddocschecks install these from npm, so they pass once thepackages are published;
docsthen gets its lockfile refreshed.