You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the readme I can pass a boolean greater-version-only, which ensures that if the latest version is, for example, 1.2.5, I cannot publish 1.2.4, even if 1.2.4 has never been published.
When running in a workflow, I get the following warning;
Is greater-version-only a valid option, and the action is just missing something in the warning condition? Or does that config option actually not exist, and is incorrectly documented?
The text was updated successfully, but these errors were encountered:
* add npm publish job
* add publish config
* temp unskip build to test
* use `if` expression on the publish step
* remove `greater-version-only`
currently doesn't work
JS-DevTools/npm-publish#52
* bump package version to test npm publish
* Revert "bump package version to test npm publish"
This reverts commit bf3f648.
* uncomment `if` expression to publish only from `main`
According to the readme I can pass a boolean
greater-version-only
, which ensures that if the latest version is, for example, 1.2.5, I cannot publish 1.2.4, even if 1.2.4 has never been published.When running in a workflow, I get the following warning;
Here's the workflow run I'm referring to.
Is
greater-version-only
a valid option, and the action is just missing something in the warning condition? Or does that config option actually not exist, and is incorrectly documented?The text was updated successfully, but these errors were encountered: