@reset, that's really a no-go. For one, it would clutter our Github organisation with a lot of extra repositories. But more importantly, the lord of the credit card (management) would never accept (private) cookbooks to take up 1 private repository each, costs would simply be way too high on GitHub.

They are all wrapper cookbooks, some have (encrypted) passwords in them, etc, etc, so there's no way we can make them public.

I really do believe a better pattern matcher would help us (and I assume others) a lot.

F.e., why not have something like `/v(?<version>\d+.*)$/`. That would pretty much guarantee the tag is an actual release tag and would be so much more flexible than the currently matcher.