When all the tagged versions for a package are prereleases, then hubcap will generate a PR, but Netflify won't be able to build it, so it can't auto-merge. This will hold up all other packages until it is resolved.
This is caused by a confluence of issues:
hubcap will generate PRs whenever there is a tag with a valid semantic version (includes both final releases as well as pre-releases)
hubcap will assign the latest final version when it can find one and "" otherwise
hub.getdbt.com requires that latest is a valid version (and will break otherwise)
Easiest solution:
Remove pre-release only packages from the Hub when they are discovered (ideally not adding them to hub.json until there is a tag with a final release)
Other solutions:
make hubcap.py robust in the face of packages with only pre-release tags
make hub.getdbt.com robust in the face of a blank latest version
I'm taking the easiest solution in the short-term and have a PR ready that implements the first "other" solution.
A problem with using the easiest solution long-term is that simple human error can trigger this situation again in the future. I'd rather prevent it entirely.
When all the tagged versions for a package are prereleases, then hubcap will generate a PR, but Netflify won't be able to build it, so it can't auto-merge. This will hold up all other packages until it is resolved.
This is caused by a confluence of issues:
latestfinal version when it can find one and""otherwiselatestis a valid version (and will break otherwise)Easiest solution:
Other solutions:
latestversionI'm taking the easiest solution in the short-term and have a PR ready that implements the first "other" solution.
A problem with using the easiest solution long-term is that simple human error can trigger this situation again in the future. I'd rather prevent it entirely.