I changed the config publish script so that the npm version will not be automatically updated. Instead circleci will perform a test to check whether the version in package.json has been updated to be greater than the version in npm. If the version hasn't been updated (which means the npm publish step would fail), then the test will fail and that will ensure that any PRs that are pushed must have an updated version. This test is performed before any other, so that the circleci test should fail early, before losing time with other tests.
I changed the config publish script so that the npm version will not be automatically updated. Instead circleci will perform a test to check whether the version in package.json has been updated to be greater than the version in npm. If the version hasn't been updated (which means the npm publish step would fail), then the test will fail and that will ensure that any PRs that are pushed must have an updated version. This test is performed before any other, so that the circleci test should fail early, before losing time with other tests.