Re-releasing the same version several times about semantic-release-action HOT 7 CLOSED

semantic-release uses Git tags to determine the commits added since the last release. If a release has been published before setting up semantic-release you must make sure the most recent commit included in the last published release is in the release branches history and is tagged with the version released, formatted according to the tag format configured (defaults to vx.y.z).

See existing version tags.

from semantic-release-action.

Unless I'm mistaken, the SR action doesn't seem to be looking at the git tag even after having it pushed to master and it even ignores more recent tags.
And it's not like I suddenly switched to using a semantic-release with semantic versions when that has been set since the start; I guess, switching from a TravisCI with SR to a GH Action approach with no version-changing commits caused the problem.
But at the same time, I've yet to find a successful way to fix that.

from semantic-release-action.

Very strangely, I checked your action log. It says "Found git tag v1.4.1 associated with version 1.4.1 on branch master". But your latest tag is v1.4.2 and the version on npm is 1.4.3.

from semantic-release-action.

The latest NPM version (1.4.3) reflects the one in the package.json (which normally should be updated by SR when needed), the v1.4.3 tag is on the master branch so SR should be able to find this.
It's weird!

from semantic-release-action.

This problem seems to have gone away, I don't know SR CI managed to release a new (minor) version to GH and NPM without updating the package.json file? I never thought this was possible.

from semantic-release-action.

I think I know where the problem is. You need to add the package.json file to the @semantic-release/git plugin. semantic-release automatically updates the package.json file before releasing it to npm, but does not commit this change to your branch.

from semantic-release-action.

Hmm, that could explain why although the latest GH release does contain the package.json which is out-of-sync.
I've noticed that according to https://github.com/semantic-release/git#examples, the @semantic-release/npm should be before the git as it's apparently where the package.json is updated.

from semantic-release-action.