v0.30

This release introduces breaking changes to the configuration syntax for labels:color:custom, instead of a one to one mapping it's now a mapping when the key is the label name, and the value is a list of matching rules. This change allows for more control when specifying which label should get which color, see #537 for details.

Old configuration syntax:

labels:
  color:
    custom:
      severity:
        info: "#87c4e0"
        warning: "#ffae42"
        critical: "#ff220c"

New syntax:

labels:
  color:
    custom:
      severity:
         - value: info
           color: "#87c4e0"
         - value: warning
           color: "#ffae42"
         - value: critical
           color: "#ff220c"

To use a regular expression for matching label values (instead of exact string comparison) set value_re, example:

- value_re: ".*"
  color: "#ffffff"

Keep in mind that the order of entries on the list is important since they are evaluated in the same order as in config, first match wins. See docs for details.

Full changelog:

• #543 fix(config): change config schema to allow regex based matches
• #542 chore(docs): update screenshots
• #541 chore(ui): use rocket icon on the upgrade screen
• #540 feat(api): allow using wildcards with custom colors
• #536 chore(backend): switch jarcoal/httpmock imports to use github
• #534 chore(ci): use Go 1.12.1 on Travis
• #532 feat(ui): add UI toggle for changing autohide settings
• #531 fix(api): always sort shared silences
• #528 fix(api): correctly deduplicate silences