fix: removing paths-ignore from action to avoid blocking releases #69
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.
This PR removes the
paths-ignore
key from the build workflow, as this may unintentionally block releases from running. Semantic-release will fail if when it comes time to publish a relase, the published commit is no longer the head commit in the repo. This is to avoid situations where an earlier commit might get a later version number than later commit if they both are merged at roughly the same time.However, if the most recent commit is just a change to the README.md for example, the
paths-ignore
can cause semantic-release to fail. If, due to the README.md change, it is no longer the most recent commit to the repo, semantic release will bail out assuming that the most recent CI run will pull in the changes and publish, but due to thepaths-ignore
, CI never gets run and thus the change never gets deployed.