This action will scan a code base and publish any public JavaScript modules it detects. It supports publishing one or more modules, custom npm registries, and custom .npmrc files.
Modules are detected by the presence of a package.json file. Private packages will not be published (unless forced) and .npmrc files will be respected if they exist within the module's root directory.
This action was designed for workflows which require variations of a module to be published under different names. For example, a Node version and a browser version of the same library.
This action serves as the last step of a multi-phase deployment process:
- Build & Test for multiple runtimes.
- Autotag new versions by updating
package.json. - Publish multiple modules (i.e., this action).