The Provider-specific changes regexp in .goreleaser.yml is a hardcoded list of provider names used to group changelog entries. When a new provider is added, this regexp must be manually updated, which is easy to forget.
- title: 'Provider-specific changes:'
regexp: "(?i)((adguardhome|akamaiedgedns|alidns|...|vultr).*:)+.*"
Auto-generating this list from the registered provider constants would solve that, but introduces a question about historical aliases. In #4072 (comment) @TomOnTime (@tlimoncelli) noted that both CLOUDFLAREAPI and the common shorthand CLOUDFLARE should be accepted. With auto-generation only CLOUDFLAREAPI would appear, since that's the registered constant. The same applies to other historical aliases like HEXONET (now CNR), GANDI (now GANDI_V5), NSONE (now NS1), etc.
How should we handle these?
The
Provider-specific changesregexp in.goreleaser.ymlis a hardcoded list of provider names used to group changelog entries. When a new provider is added, this regexp must be manually updated, which is easy to forget.Auto-generating this list from the registered provider constants would solve that, but introduces a question about historical aliases. In #4072 (comment) @TomOnTime (@tlimoncelli) noted that both
CLOUDFLAREAPIand the common shorthandCLOUDFLAREshould be accepted. With auto-generation onlyCLOUDFLAREAPIwould appear, since that's the registered constant. The same applies to other historical aliases likeHEXONET(nowCNR),GANDI(nowGANDI_V5),NSONE(nowNS1), etc.How should we handle these?