Repository navigation
Publish TreeDataGridWeb 0.1.0 to npm with verified release artifacts - #1
Merged
Merged
Conversation
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.
Publish the existing Core models and browser control together as
@wieslawsoltes/treedatagridweb@0.1.0. The root and/coreentry points share the same DOM-independent constructors;/webpreserves their identity inside the native component. The package includes declarations, CSS, global/standalone assets and notices.The existing Pages pipeline now verifies Node 22 and Node 24, tests isolated installed consumers, creates immutable release archives/checksums, and calls npm publication using the release tag and verified commit. Publication uses provenance and checks release/npm byte identity, registry indexes and tags, downloaded package consumers, and a fresh anonymous installation. Retries retain existing release assets and skip an already-identical npm version. README installation instructions and status badges now describe the published package.
Validation: 36 core/registry tests, strict declarations, HTTP checks and isolated installed ESM/CommonJS/TypeScript/assets consumers pass locally. CI additionally gates the existing Chromium showcase and installed browser component before merging. No runtime feature-parity claims are changed.