fix: publishing #1246
Merged
fix: publishing #1246
+1 −3
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
kirillzyusko changed the title 
Contributor
📊 Package size report
|
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.
📜 Description
Fixed publishing workflow.
💡 Motivation and Context
Recently npmjs restricted usage of classic tokens. As a result all workflows that were dependent on it are failing now.
In this PR I'm migrating to the official way of publishing packages from GH actions.
📢 Changelog
CI
🤔 How Has This Been Tested?
Tested via this PR.
📸 Screenshots (if appropriate):
📝 Checklist