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
My GitHub Action automatically updates my package.json with the correct version number based on the changes that were done during that release. Recently I noticed that what is being published to NPM doesn't align with the version in my package.json.
Below is my workflow for deploying to NPM. This step is done after built, version bumped, changelog and a release created in GitHub. I've been able to verify that my version is bumping correctly and the changelog + GitHub is reflecting this.
I would expect that this deploy action would take it's version from package.json which is correct but it appears as if it's looking to npm and just bumping whatever is already there?
I figured out what was going on here, I changed my default branch to be develop instead of master so this action was taking the sha from the wrong branch.
My GitHub Action automatically updates my
package.json
with the correct version number based on the changes that were done during that release. Recently I noticed that what is being published to NPM doesn't align with the version in mypackage.json
.Below is my workflow for deploying to NPM. This step is done after built, version bumped, changelog and a release created in GitHub. I've been able to verify that my version is bumping correctly and the changelog + GitHub is reflecting this.
I would expect that this deploy action would take it's
version
frompackage.json
which is correct but it appears as if it's looking tonpm
and just bumping whatever is already there?Deploy to NPM Workflow
The text was updated successfully, but these errors were encountered: