Publish npm package from packed tgz artifact#1148
Merged
mpreyskurantov merged 2 commits intoJun 12, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the npm publishing workflow to publish from pre-packed .tgz artifacts (instead of publishing workspace packages directly), aligning with the “trusted publishing” approach referenced in #1119 and the linked similar PR.
Changes:
- Replace workspace-wide
pnpm publishwith an explicitpackstep per package. - Publish
devextreme-clianddevextreme-schematicsfrom the generated tarballs, keeping--provenanceand supportingdry-run.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
alexslavr
approved these changes
Jun 12, 2026
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.
Patch for:
Similar to
devextreme-exceljs-fork#78: