gotjosh

Additionally, we should add examples on what these outputs look like as right now they vary greatly per action.

To expand on this, it seems that running sync/diff after syncing will also result in updates - I would have expected this to no-op.

I don't think this is just the `ValidateGroup` function, there's also the logql parser for linting of rules that's importing a big portion of loki.

At the moment, we have three binaries. We should consider having independent release process for all of them.

Steps to create the release: 1. Manually build and test the new additions 2. Create a new tag based on: ``` $ tag=v0.2.1 $ git tag -s "${tag}" -m "${tag}"...

Partially done by #84

Sorry @ritaCanavarro, I didn't see this issue - I have filed #79 to fix it.

[One more example failure](https://github.com/grafana/mimir/actions/runs/9582438531/job/26421602199)

> Should we update the documentation [here](https://prometheus.io/docs/prometheus/latest/configuration/recording_rules/) and [here](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/), to mention the new field in the rules config file? I have updated the docs in [here](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) as this is where...

@juliusv @roidelapluie @bwplotka @beorn7 @ArthurSens any thoughts?