feat: Add Grafana auto-update & improve classifier

Add auto-update for Grafana on Synology via SSH + docker compose,
with review examples and a context.txt describing the specific setup
(Prometheus + Node Exporter, no plugins) so the classifier can
ignore plugin-only breaking changes.

The classifier now loads an optional context.txt per service to
tailor decisions to the actual deployment. It also truncates large
release notes intelligently, keeping important sections (breaking
changes, deprecations, migration notes) while dropping long PR
lists that add no signal.

test_classifier.py now also loads context.txt and accepts any
service name as argument.
This commit is contained in:
Jeena 2026-04-13 03:57:22 +00:00
parent 67a9509eaa
commit ea90b8569b
10 changed files with 185 additions and 1 deletions

View file

@ -0,0 +1,16 @@
action: manual
reason: Major version changes secret encryption so data source credentials created with v9+ cannot be decrypted by older versions. Rollback becomes difficult. Admin should back up the database before upgrading. Also changes log format which may affect monitoring.
---
[Download page](https://grafana.com/grafana/download/9.0.0)
[What's new highlights](https://grafana.com/docs/grafana/latest/whatsnew/)
### Breaking changes
* Any secret (data sources credential, alert manager credential, etc, etc) created or modified with Grafana v9.0 won't be decryptable from any previous version (by default) because the way encrypted secrets are stored into the database has changed. Although secrets created or modified with previous versions will still be decryptable by Grafana v9.0.
* If required, although generally discouraged, the `disableEnvelopeEncryption` feature toggle can be enabled to keep envelope encryption disabled once updating to Grafana v9.0.
* In case of need to rollback to an earlier version of Grafana (i.e. Grafana v8.x) for any reason, after being created or modified any secret with Grafana v9.0, the `envelopeEncryption` feature toggle will need to be enabled to keep backwards compatibility.
* Alternatively, backing up the Grafana database before updating could be a good idea to prevent disasters.
The format of log messages have been updated, `lvl` is now `level` and `eror` and `dbug` has been replaced with `error` and `debug`. The precision of timestamps has been increased. To smooth the transition, it is possible to opt-out of the new log format by enabling the feature toggle `oldlog`. This option will be removed in a future minor release.
The `Rename by regex` transformation has been improved to allow global patterns of the form `/<stringToReplace>/g`. Depending on the regex match used, this may cause some transformations to behave slightly differently.