We have a recurring issue that you often forget to bump the package version number in a PR, and then when you merge it to master, the package publication fails because the version you're trying to publish already exists.
This adds a check to CI which detects these issues early and fails the CI, so you can't merge those PRs without bumping the package version number.
It gets skipped if the title of the PR is docs: ..., because such PRs don't trigger package publication when merged.
We have a recurring issue that you often forget to bump the package version number in a PR, and then when you merge it to
master
, the package publication fails because the version you're trying to publish already exists.This adds a check to CI which detects these issues early and fails the CI, so you can't merge those PRs without bumping the package version number.
It gets skipped if the title of the PR is
docs: ...
, because such PRs don't trigger package publication when merged.Same as https://github.com/apify/apify-sdk-python/pull/127.