Lint errors for bumped build number if PR made shortly after merge of new version #1007
Description
It seems that lint errors if you:
- release a new version of a package
- then make a PR with the same version and build number updated, i.e. to 1
The lint error is:
ERROR: recipes/pathogen-embed/meta.yaml:13: build_number_needs_reset: The recipe build number should be reset to 0
It seems that the "build_number_needs_reset" rule is unaware of the recently released new version
This can't be worked around by setting the build number to 0, because then a different lint rule fires that complains about lack of bump of number.
As a result, it appears as if we can't make a successful PR with build number bumped after version bump until the new version has percolated to CDN.