ci(publish): try to fix npm publish error #475
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
После #466 публикация падает с ошибкой: ``` npm error code E404 npm error 404 Not Found - PUT https://registry.npmjs.org/swc-plugin-css-modules - Not found npm error 404 npm error 404 'swc-plugin-css-modules@7.1.0' is not in this registry. ``` В npm/cli#8730 (comment) указано, что возможно причина в версии NodeJS да и `@actions/setup-node@v6` требует NodeJS >= 24. Поэтому создал файл `.nvmrc` с нужной версией и заменил параметр `node-version` на `node-version-file` у `@actions/setup-node`. В будущем можно будет править версию через этот файл, а не через изменение воркфлоу. Поправил по ходу дела: - `@actions/setup-node` рекомендует использовать `contents: read` - в `package.json` поправил `repository.url`, чтобы поправить предупреждение ` npm auto-corrected some errors in your package.json when publishing`; - удалил `provenance` из `package.json`, т.к. больше не нужен, также оно автоматически включено при использовании [Trusted Publishing](https://docs.npmjs.com/trusted-publishers#automatic-provenance-generation).
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #475 +/- ##
=======================================
Coverage 84.50% 84.50%
=======================================
Files 6 6
Lines 426 426
Branches 15 15
=======================================
Hits 360 360
Misses 51 51
Partials 15 15 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
SevereCloud
approved these changes
Nov 25, 2025
promo4ka
approved these changes
Nov 25, 2025
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.
После #466 публикация падает с ошибкой:
В npm/cli#8730 (comment) указано, что возможно причина в версии NodeJS да и
@actions/setup-node@v6требует NodeJS >= 24.Поэтому создал файл
.nvmrcс нужной версией и заменил параметрnode-versionнаnode-version-fileу@actions/setup-node. В будущем можно будет править версию через этот файл, а не через изменение воркфлоу.Поправил по ходу дела:
@actions/setup-nodeрекомендует использоватьcontents: readpackage.jsonпоправилrepository.url, чтобы поправить предупреждениеnpm auto-corrected some errors in your package.json when publishing;provenanceизpackage.json, т.к. больше не нужен, также оно автоматически включено при использовании Trusted Publishing.