Release Notes
Full Changelog on GitHub View all releases on GitHub
v0.68.1v0.68.1
## What's Changed
## 📚 Documentation
- chore(plans): archive 9 completed plans to docs/Plans/completed/ @Wiesenwischer (#411)
## 🧰 Maintenance
- chore(plans): archive 9 completed plans to docs/Plans/completed/ @Wiesenwischer (#411)
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.68.0...v0.68.1
## 📚 Documentation
- chore(plans): archive 9 completed plans to docs/Plans/completed/ @Wiesenwischer (#411)
## 🧰 Maintenance
- chore(plans): archive 9 completed plans to docs/Plans/completed/ @Wiesenwischer (#411)
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.68.0...v0.68.1
v0.68.0v0.68.0
## What's Changed
## 🚀 Features
- feat(snmp): expand OID reference to per-column rows with concrete OIDs @Wiesenwischer (#410)
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.67.0...v0.68.0
## 🚀 Features
- feat(snmp): expand OID reference to per-column rows with concrete OIDs @Wiesenwischer (#410)
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.67.0...v0.68.0
v0.67.0 – IANA Private Enterprise Number 65846v0.67.0
## 🎉 IANA assigned ReadyStackGo Private Enterprise Number 65846
IANA confirmed our PEN assignment on **2026-05-21**:
> Decimal: **65846**
> Organization: ReadyStackGo
> Contact: Marcus Dammann
> Email: dev@wiesenwischer.de
> Registry: https://www.iana.org/assignments/enterprise-numbers/
The placeholder PEN \`99999\` that has been in use since v0.64 is replaced everywhere. The SNMP root OID is now **\`1.3.6.1.4.1.65846.1\`**.
## ⚠️ Breaking change — operators must act
If you have been polling RSGO via SNMP under the placeholder PEN, you need to re-point your monitoring tools to the real PEN.
| Setup | Action |
|-------|--------|
| **SNMPv2c / SNMPv3 polling** (Nagios, Zabbix, snmpwalk) | Re-import \`READYSTACKGO-MIB.txt\` (Settings → SNMP → Download MIB, or \`GET /api/snmp/mib\`). Replace \`99999.*\` with \`65846.*\` in saved OID strings. |
| **PRTG Variant 1** (Device Template Bundle) | Re-download the bundle and unpack into the PRTG install dir. |
| **PRTG Variant 4** (HTTP Data Advanced sensor) | Nothing — JSON channel names did not change. |
| **PRTG Variant 2 + 3** (auto-register) | Re-deploy or unlink+relink affected ProductDeployments to refresh PRTG devices against the new OIDs. |
| **Custom \`snmpwalk\` scripts** | Replace \`99999\` with \`65846\`. |
## 🔄 Auto-migration in RSGO
The new EF migration **\`MigrateRootOidToAssignedPen\`** flips \`SnmpSettings.RootOid\` from the placeholder to the assigned PEN on container start. Customers who set a custom \`RootOid\` (their own corporate PEN) are **not** touched.
**SNMPv3 USM engine IDs are deliberately NOT regenerated.** The engine ID is folded into every v3 USM key — a reset would invalidate every v3 user's auth/priv credentials. Only fresh agents (no \`EngineIdHex\` stored yet) get an engine ID rooted at the new PEN; existing v3 polling keeps working unchanged.
## 📦 Pull request
- [#409](https://github.com/Wiesenwischer/ReadyStackGo/pull/409) — feat(snmp): migrate to IANA-assigned PEN 65846
## 🧪 Verification
- 2953 unit tests passing
- \`smilint\` CI passes on the updated MIB
- Live smoke test on a fresh container: wizard, SNMP settings default RootOid, \`/api/snmp/oid-reference\`, MIB anchor — all rooted at \`65846\`
- Doc-screenshot Playwright spec re-run; UI captures (OID-reference, PRTG bundle card, PRTG-HTTP card, settings tile) updated to show the assigned PEN
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.66.1...v0.67.0
IANA confirmed our PEN assignment on **2026-05-21**:
> Decimal: **65846**
> Organization: ReadyStackGo
> Contact: Marcus Dammann
> Email: dev@wiesenwischer.de
> Registry: https://www.iana.org/assignments/enterprise-numbers/
The placeholder PEN \`99999\` that has been in use since v0.64 is replaced everywhere. The SNMP root OID is now **\`1.3.6.1.4.1.65846.1\`**.
## ⚠️ Breaking change — operators must act
If you have been polling RSGO via SNMP under the placeholder PEN, you need to re-point your monitoring tools to the real PEN.
| Setup | Action |
|-------|--------|
| **SNMPv2c / SNMPv3 polling** (Nagios, Zabbix, snmpwalk) | Re-import \`READYSTACKGO-MIB.txt\` (Settings → SNMP → Download MIB, or \`GET /api/snmp/mib\`). Replace \`99999.*\` with \`65846.*\` in saved OID strings. |
| **PRTG Variant 1** (Device Template Bundle) | Re-download the bundle and unpack into the PRTG install dir. |
| **PRTG Variant 4** (HTTP Data Advanced sensor) | Nothing — JSON channel names did not change. |
| **PRTG Variant 2 + 3** (auto-register) | Re-deploy or unlink+relink affected ProductDeployments to refresh PRTG devices against the new OIDs. |
| **Custom \`snmpwalk\` scripts** | Replace \`99999\` with \`65846\`. |
## 🔄 Auto-migration in RSGO
The new EF migration **\`MigrateRootOidToAssignedPen\`** flips \`SnmpSettings.RootOid\` from the placeholder to the assigned PEN on container start. Customers who set a custom \`RootOid\` (their own corporate PEN) are **not** touched.
**SNMPv3 USM engine IDs are deliberately NOT regenerated.** The engine ID is folded into every v3 USM key — a reset would invalidate every v3 user's auth/priv credentials. Only fresh agents (no \`EngineIdHex\` stored yet) get an engine ID rooted at the new PEN; existing v3 polling keeps working unchanged.
## 📦 Pull request
- [#409](https://github.com/Wiesenwischer/ReadyStackGo/pull/409) — feat(snmp): migrate to IANA-assigned PEN 65846
## 🧪 Verification
- 2953 unit tests passing
- \`smilint\` CI passes on the updated MIB
- Live smoke test on a fresh container: wizard, SNMP settings default RootOid, \`/api/snmp/oid-reference\`, MIB anchor — all rooted at \`65846\`
- Doc-screenshot Playwright spec re-run; UI captures (OID-reference, PRTG bundle card, PRTG-HTTP card, settings tile) updated to show the assigned PEN
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.66.1...v0.67.0
v0.66.1 – PRTG deployment-detail screenshotsv0.66.1
## 📚 Documentation
Closes the V2 follow-up item from the v0.66.0 release notes:
- **Inline-tab screenshot** ([prtg-detail-inline-tab.png](https://github.com/Wiesenwischer/ReadyStackGo/blob/main/src/ReadyStackGo.PublicWeb/public/images/docs/prtg-detail-inline-tab.png)) replaces the V3-add-form placeholder in [\`docs/monitoring/snmp/prtg-inline\`](https://readystackgo.dev/de/docs/monitoring/snmp/prtg-inline).
- **Saved-connection-tab screenshot** ([prtg-detail-saved-tab.png](https://github.com/Wiesenwischer/ReadyStackGo/blob/main/src/ReadyStackGo.PublicWeb/public/images/docs/prtg-detail-saved-tab.png)) added to [\`docs/monitoring/snmp/prtg-connection\`](https://readystackgo.dev/de/docs/monitoring/snmp/prtg-connection).
## 🧪 Tests
\`e2e/prtg-integration.spec.ts\` gains a serial test block that reuses the \`ensureE2ePlatformDeployed\` helper pattern from \`maintenance-mode.spec.ts\` — POSTs the stack source, syncs, deploys, polls up to 60 s for Running, then captures both tabs of the PRTG monitoring card. Skips cleanly in CI when no docker-compose container is available.
## 📦 Pull requests
- [#408](https://github.com/Wiesenwischer/ReadyStackGo/pull/408) — docs(prtg): close V2 follow-up — deployment-detail screenshots
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.66.0...v0.66.1
Closes the V2 follow-up item from the v0.66.0 release notes:
- **Inline-tab screenshot** ([prtg-detail-inline-tab.png](https://github.com/Wiesenwischer/ReadyStackGo/blob/main/src/ReadyStackGo.PublicWeb/public/images/docs/prtg-detail-inline-tab.png)) replaces the V3-add-form placeholder in [\`docs/monitoring/snmp/prtg-inline\`](https://readystackgo.dev/de/docs/monitoring/snmp/prtg-inline).
- **Saved-connection-tab screenshot** ([prtg-detail-saved-tab.png](https://github.com/Wiesenwischer/ReadyStackGo/blob/main/src/ReadyStackGo.PublicWeb/public/images/docs/prtg-detail-saved-tab.png)) added to [\`docs/monitoring/snmp/prtg-connection\`](https://readystackgo.dev/de/docs/monitoring/snmp/prtg-connection).
## 🧪 Tests
\`e2e/prtg-integration.spec.ts\` gains a serial test block that reuses the \`ensureE2ePlatformDeployed\` helper pattern from \`maintenance-mode.spec.ts\` — POSTs the stack source, syncs, deploys, polls up to 60 s for Running, then captures both tabs of the PRTG monitoring card. Skips cleanly in CI when no docker-compose container is available.
## 📦 Pull requests
- [#408](https://github.com/Wiesenwischer/ReadyStackGo/pull/408) — docs(prtg): close V2 follow-up — deployment-detail screenshots
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.66.0...v0.66.1
v0.66.0 – PRTG Network Monitor integration (4 variants)v0.66.0
## 🎯 Headline
**Complete PRTG Network Monitor integration in four variants.** Pick the one that matches your operational style — they coexist and you can mix-and-match per deployment.
## The four variants at a glance
| | Setup time | RSGO calls PRTG? | Granularity | Best for |
|---|---|---|---|---|
| **V1 — Device Template Bundle** | 10–15 min (admin elevated, probe restart) | No | Per-stack / per-service sensors | Established PRTG shops that want deep integration |
| **V4 — HTTP Data Advanced sensor** | ~5 min (one PRTG sensor) | No | 13 aggregated channels in one sensor | "Just want to see all-green / all-red", no PRTG-server admin rights |
| **V3 — `PrtgConnection` resource** | 5 min (Settings → PRTG Connections) | Yes, auto-register on deploy | Per-deployment device from a template | Many deployments, central PRTG, want clean auto-cleanup on remove |
| **V2 — Inline registration** | 1 min (deployment detail page) | Yes, auto-register on deploy | Per-deployment device from a template | Multi-tenant or one-off setups, no shared connection wanted |
## ✨ Features
- **V1: One-click PRTG Device Template Bundle download** ([#402](https://github.com/Wiesenwischer/ReadyStackGo/pull/402))
`GET /api/snmp/prtg-bundle` streams a ZIP with a PRTG device template, the MIB and value-lookup files generated from the domain enums. Unpack into the PRTG install dir, run Auto-Discovery, done. Dynamic RootOid substitution so customers with their own IANA PEN get a bundle that points at their OIDs.
- **V4: One-sensor PRTG integration via HTTP Data Advanced** ([#404](https://github.com/Wiesenwischer/ReadyStackGo/pull/404))
`GET /api/integrations/prtg/status` returns 13 aggregated channels in PRTG's HTTP Data Advanced JSON shape. Paste the URL into a single PRTG sensor — no file copies, no probe restart, no MIB import. API key works via header **or** query parameter (PRTG sensors cannot inject headers, so the query-string transport is what makes one-URL setup possible).
- **V3: `PrtgConnection` resource + auto-register lifecycle** ([#405](https://github.com/Wiesenwischer/ReadyStackGo/pull/405))
New domain aggregate `PrtgConnection` (URL + encrypted API token + optional template device id). Full CRUD UI at `/settings/prtg-connections`. ProductDeployments can be linked; lifecycle handlers automatically `duplicateobject.htm` on Running, `pause.htm` to unpause, `deleteobject.htm` on Removed/Superseded. All best-effort: a PRTG outage logs a warning and lets the RSGO deploy continue.
- **V2: Inline ad-hoc PRTG registration + Deployment-Detail UI** ([#406](https://github.com/Wiesenwischer/ReadyStackGo/pull/406))
Per-deployment URL + token (encrypted at rest, never echoed back) for multi-tenant setups. New tabbed **"PRTG monitoring"** card on every ProductDeployment detail page with "Saved connection" (V3) and "Inline (ad-hoc)" (V2) tabs. Only one PRTG target active at a time — switching tabs cleanly clears the other side.
## 🔐 Security
- All PRTG API tokens (V2 inline, V3 saved connection) are encrypted at rest with the same `ICredentialEncryptionService` that protects Docker registry credentials and SNMPv3 passphrases.
- Tokens never appear in any read DTO. `HasInlinePrtgApiToken: bool` and `HasApiToken: bool` are the only indicators that a token is set.
- Per-connection TLS verification toggle so self-signed PRTG certs work without disabling validation globally.
- API-key handler in `ApiKeyAuthenticationHandler` now accepts the key via the `?apikey=` query parameter in addition to the `X-Api-Key` header — limited to one purpose (PRTG-style URL-only sensors) but documented as a generic option in the auth pipeline.
## 📚 Documentation
Eight new pages, all DE + EN, all with screenshots:
- [`docs/monitoring/snmp/prtg`](https://readystackgo.dev/de/docs/monitoring/snmp/prtg) — V1 Device Template Bundle ([#402](https://github.com/Wiesenwischer/ReadyStackGo/pull/402))
- [`docs/monitoring/snmp/prtg-http-sensor`](https://readystackgo.dev/de/docs/monitoring/snmp/prtg-http-sensor) — V4 HTTP Data Advanced ([#404](https://github.com/Wiesenwischer/ReadyStackGo/pull/404))
- [`docs/monitoring/snmp/prtg-connection`](https://readystackgo.dev/de/docs/monitoring/snmp/prtg-connection) — V3 PrtgConnection ([#405](https://github.com/Wiesenwischer/ReadyStackGo/pull/405))
- [`docs/monitoring/snmp/prtg-inline`](https://readystackgo.dev/de/docs/monitoring/snmp/prtg-inline) — V2 Inline ([#406](https://github.com/Wiesenwischer/ReadyStackGo/pull/406))
Screenshots captured via a new Playwright spec ([#407](https://github.com/Wiesenwischer/ReadyStackGo/pull/407)) so the docs stay in sync with the UI on every re-run.
## ⚠️ Migration notes
- Two new EF Core migrations: `AddPrtgConnections` (V3 — new `PrtgConnections` table + 3 columns on `ProductDeployments`) and `AddInlinePrtgRegistration` (V2 — 4 inline columns on `ProductDeployments`). Both auto-apply on container start. Legacy databases (pre-EF-migration era) need the migration-baseline path which was updated to handle this case.
- No breaking changes. All four variants are opt-in: nothing happens until you create a connection (V3) or set inline credentials (V2), download the bundle (V1), or add a PRTG sensor against the new endpoint (V4).
## 🧪 Tests
- **2953 unit tests** passing across the four PRs (14 new tests for V4 alone, plus V3 + V2 coverage)
- New E2E Playwright spec captures the documentation screenshots reproducibly
- Live smoke tests against the docker-compose container verify every new endpoint
- Manual PRTG-trial-instance integration verifies V1+V4; V3 + V2 are wire-level tested but a real PRTG round-trip is the follow-up
## 📦 Pull requests in this release
- [#402](https://github.com/Wiesenwischer/ReadyStackGo/pull/402) — feat(snmp): one-click PRTG integration bundle download
- [#403](https://github.com/Wiesenwischer/ReadyStackGo/pull/403) — docs(plans): add Variant 4 — PRTG HTTP Data Advanced sensor
- [#404](https://github.com/Wiesenwischer/ReadyStackGo/pull/404) — feat(prtg): one-sensor PRTG integration via HTTP Data Advanced (Variant 4)
- [#405](https://github.com/Wiesenwischer/ReadyStackGo/pull/405) — feat(prtg): PrtgConnection aggregate + auto-register lifecycle (Variant 3)
- [#406](https://github.com/Wiesenwischer/ReadyStackGo/pull/406) — feat(prtg): deployment-detail UI + inline PRTG registration (Variant 2)
- [#407](https://github.com/Wiesenwischer/ReadyStackGo/pull/407) — docs(prtg): add screenshots to all four PRTG integration variants
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.65.4...v0.66.0
**Complete PRTG Network Monitor integration in four variants.** Pick the one that matches your operational style — they coexist and you can mix-and-match per deployment.
## The four variants at a glance
| | Setup time | RSGO calls PRTG? | Granularity | Best for |
|---|---|---|---|---|
| **V1 — Device Template Bundle** | 10–15 min (admin elevated, probe restart) | No | Per-stack / per-service sensors | Established PRTG shops that want deep integration |
| **V4 — HTTP Data Advanced sensor** | ~5 min (one PRTG sensor) | No | 13 aggregated channels in one sensor | "Just want to see all-green / all-red", no PRTG-server admin rights |
| **V3 — `PrtgConnection` resource** | 5 min (Settings → PRTG Connections) | Yes, auto-register on deploy | Per-deployment device from a template | Many deployments, central PRTG, want clean auto-cleanup on remove |
| **V2 — Inline registration** | 1 min (deployment detail page) | Yes, auto-register on deploy | Per-deployment device from a template | Multi-tenant or one-off setups, no shared connection wanted |
## ✨ Features
- **V1: One-click PRTG Device Template Bundle download** ([#402](https://github.com/Wiesenwischer/ReadyStackGo/pull/402))
`GET /api/snmp/prtg-bundle` streams a ZIP with a PRTG device template, the MIB and value-lookup files generated from the domain enums. Unpack into the PRTG install dir, run Auto-Discovery, done. Dynamic RootOid substitution so customers with their own IANA PEN get a bundle that points at their OIDs.
- **V4: One-sensor PRTG integration via HTTP Data Advanced** ([#404](https://github.com/Wiesenwischer/ReadyStackGo/pull/404))
`GET /api/integrations/prtg/status` returns 13 aggregated channels in PRTG's HTTP Data Advanced JSON shape. Paste the URL into a single PRTG sensor — no file copies, no probe restart, no MIB import. API key works via header **or** query parameter (PRTG sensors cannot inject headers, so the query-string transport is what makes one-URL setup possible).
- **V3: `PrtgConnection` resource + auto-register lifecycle** ([#405](https://github.com/Wiesenwischer/ReadyStackGo/pull/405))
New domain aggregate `PrtgConnection` (URL + encrypted API token + optional template device id). Full CRUD UI at `/settings/prtg-connections`. ProductDeployments can be linked; lifecycle handlers automatically `duplicateobject.htm` on Running, `pause.htm` to unpause, `deleteobject.htm` on Removed/Superseded. All best-effort: a PRTG outage logs a warning and lets the RSGO deploy continue.
- **V2: Inline ad-hoc PRTG registration + Deployment-Detail UI** ([#406](https://github.com/Wiesenwischer/ReadyStackGo/pull/406))
Per-deployment URL + token (encrypted at rest, never echoed back) for multi-tenant setups. New tabbed **"PRTG monitoring"** card on every ProductDeployment detail page with "Saved connection" (V3) and "Inline (ad-hoc)" (V2) tabs. Only one PRTG target active at a time — switching tabs cleanly clears the other side.
## 🔐 Security
- All PRTG API tokens (V2 inline, V3 saved connection) are encrypted at rest with the same `ICredentialEncryptionService` that protects Docker registry credentials and SNMPv3 passphrases.
- Tokens never appear in any read DTO. `HasInlinePrtgApiToken: bool` and `HasApiToken: bool` are the only indicators that a token is set.
- Per-connection TLS verification toggle so self-signed PRTG certs work without disabling validation globally.
- API-key handler in `ApiKeyAuthenticationHandler` now accepts the key via the `?apikey=` query parameter in addition to the `X-Api-Key` header — limited to one purpose (PRTG-style URL-only sensors) but documented as a generic option in the auth pipeline.
## 📚 Documentation
Eight new pages, all DE + EN, all with screenshots:
- [`docs/monitoring/snmp/prtg`](https://readystackgo.dev/de/docs/monitoring/snmp/prtg) — V1 Device Template Bundle ([#402](https://github.com/Wiesenwischer/ReadyStackGo/pull/402))
- [`docs/monitoring/snmp/prtg-http-sensor`](https://readystackgo.dev/de/docs/monitoring/snmp/prtg-http-sensor) — V4 HTTP Data Advanced ([#404](https://github.com/Wiesenwischer/ReadyStackGo/pull/404))
- [`docs/monitoring/snmp/prtg-connection`](https://readystackgo.dev/de/docs/monitoring/snmp/prtg-connection) — V3 PrtgConnection ([#405](https://github.com/Wiesenwischer/ReadyStackGo/pull/405))
- [`docs/monitoring/snmp/prtg-inline`](https://readystackgo.dev/de/docs/monitoring/snmp/prtg-inline) — V2 Inline ([#406](https://github.com/Wiesenwischer/ReadyStackGo/pull/406))
Screenshots captured via a new Playwright spec ([#407](https://github.com/Wiesenwischer/ReadyStackGo/pull/407)) so the docs stay in sync with the UI on every re-run.
## ⚠️ Migration notes
- Two new EF Core migrations: `AddPrtgConnections` (V3 — new `PrtgConnections` table + 3 columns on `ProductDeployments`) and `AddInlinePrtgRegistration` (V2 — 4 inline columns on `ProductDeployments`). Both auto-apply on container start. Legacy databases (pre-EF-migration era) need the migration-baseline path which was updated to handle this case.
- No breaking changes. All four variants are opt-in: nothing happens until you create a connection (V3) or set inline credentials (V2), download the bundle (V1), or add a PRTG sensor against the new endpoint (V4).
## 🧪 Tests
- **2953 unit tests** passing across the four PRs (14 new tests for V4 alone, plus V3 + V2 coverage)
- New E2E Playwright spec captures the documentation screenshots reproducibly
- Live smoke tests against the docker-compose container verify every new endpoint
- Manual PRTG-trial-instance integration verifies V1+V4; V3 + V2 are wire-level tested but a real PRTG round-trip is the follow-up
## 📦 Pull requests in this release
- [#402](https://github.com/Wiesenwischer/ReadyStackGo/pull/402) — feat(snmp): one-click PRTG integration bundle download
- [#403](https://github.com/Wiesenwischer/ReadyStackGo/pull/403) — docs(plans): add Variant 4 — PRTG HTTP Data Advanced sensor
- [#404](https://github.com/Wiesenwischer/ReadyStackGo/pull/404) — feat(prtg): one-sensor PRTG integration via HTTP Data Advanced (Variant 4)
- [#405](https://github.com/Wiesenwischer/ReadyStackGo/pull/405) — feat(prtg): PrtgConnection aggregate + auto-register lifecycle (Variant 3)
- [#406](https://github.com/Wiesenwischer/ReadyStackGo/pull/406) — feat(prtg): deployment-detail UI + inline PRTG registration (Variant 2)
- [#407](https://github.com/Wiesenwischer/ReadyStackGo/pull/407) — docs(prtg): add screenshots to all four PRTG integration variants
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.65.4...v0.66.0
v0.65.4 – SNMP feature fixes + full documentationv0.65.4
## What's Changed
This release makes the SNMP feature (v0.64/v0.65) actually usable on a fresh install and ships full beginner-friendly documentation for it.
### 🐛 Bug Fixes
- **fix(snmp): make container start and v3 user form work** ([#399](https://github.com/Wiesenwischer/ReadyStackGo/pull/399))
- DI lifetime: ``HealthCheckStrategyFactory`` is now Scoped — the container no longer crashes on startup with "Cannot consume scoped service from singleton"
- FastEndpoints now serialises enums as strings — the SNMPv3 user form no longer fails with "could not be converted to SnmpAuthProtocol"
### 📚 Documentation
- **docs(snmp): add full SNMP monitoring documentation** ([#400](https://github.com/Wiesenwischer/ReadyStackGo/pull/400))
- New beginner-friendly walk-through at **/docs/monitoring/snmp** (DE + EN) — setup, polling, traps, **PRTG integration**
- Three deep-dive pages: SNMP history & versions, security models (community vs. USM), auth + priv algorithm guidance
- Landing-page tile with NEW badge
- 9 screenshots + Playwright E2E spec for the SNMP settings page
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.65.3...v0.65.4
This release makes the SNMP feature (v0.64/v0.65) actually usable on a fresh install and ships full beginner-friendly documentation for it.
### 🐛 Bug Fixes
- **fix(snmp): make container start and v3 user form work** ([#399](https://github.com/Wiesenwischer/ReadyStackGo/pull/399))
- DI lifetime: ``HealthCheckStrategyFactory`` is now Scoped — the container no longer crashes on startup with "Cannot consume scoped service from singleton"
- FastEndpoints now serialises enums as strings — the SNMPv3 user form no longer fails with "could not be converted to SnmpAuthProtocol"
### 📚 Documentation
- **docs(snmp): add full SNMP monitoring documentation** ([#400](https://github.com/Wiesenwischer/ReadyStackGo/pull/400))
- New beginner-friendly walk-through at **/docs/monitoring/snmp** (DE + EN) — setup, polling, traps, **PRTG integration**
- Three deep-dive pages: SNMP history & versions, security models (community vs. USM), auth + priv algorithm guidance
- Landing-page tile with NEW badge
- 9 screenshots + Playwright E2E spec for the SNMP settings page
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.65.3...v0.65.4
v0.65.3 – upgrade & catalog UX fixesv0.65.3
## What's Changed
## 🐛 Bug Fixes
- fix(catalog): make product cards clickable, drop View Details button @Wiesenwischer (#398)
- fix(deployments): mark old ProductDeployment as Superseded on upgrade @Wiesenwischer (#397)
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.65.2...v0.65.3
## 🐛 Bug Fixes
- fix(catalog): make product cards clickable, drop View Details button @Wiesenwischer (#398)
- fix(deployments): mark old ProductDeployment as Superseded on upgrade @Wiesenwischer (#397)
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.65.2...v0.65.3
v0.65.2 – maintenance mode UX fixesv0.65.2
## What's Changed
## 🐛 Bug Fixes
- fix(ui): ProductDeployment detail page live-updates on health + operation mode changes @Wiesenwischer (#396)
- fix(health-dashboard): show Maintenance badge on product header @Wiesenwischer (#395)
- fix(notifications): suppress per-service health alerts while product is in maintenance @Wiesenwischer (#394)
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.65.1...v0.65.2
## 🐛 Bug Fixes
- fix(ui): ProductDeployment detail page live-updates on health + operation mode changes @Wiesenwischer (#396)
- fix(health-dashboard): show Maintenance badge on product header @Wiesenwischer (#395)
- fix(notifications): suppress per-service health alerts while product is in maintenance @Wiesenwischer (#394)
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.65.1...v0.65.2
v0.65.1 – maintenance observer notificationv0.65.1
## What's Changed
## 🐛 Bug Fixes
- fix(notifications): warn admin when maintenance observer drops on unresolved variables @Wiesenwischer (#390)
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.65.0...v0.65.1
## 🐛 Bug Fixes
- fix(notifications): warn admin when maintenance observer drops on unresolved variables @Wiesenwischer (#390)
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.65.0...v0.65.1
v0.65.0 – SNMP feature completion: v3 responses, DB-backed settings + v3 users, edit UI, traps, smilint CIv0.65.0
## What's Changed in v0.65.0
- SNMP Completion (v0.65): editable settings, traps, full v3 responses (#387)
- SNMP Completion (v0.65): editable settings, traps, full v3 responses (#387)
v0.64.0 – SNMP support for monitoring deploymentsv0.64.0
## What's Changed in v0.64.0
- SNMP Agent for Deployment Monitoring (v0.64) (#381)
- SNMP Agent: deployment health via SNMP v2c/v3 polling (#377)
- SNMP Agent for Deployment Monitoring (v0.64) (#381)
- SNMP Agent: deployment health via SNMP v2c/v3 polling (#377)
v0.62.5 – Boolean toggle layout fixv0.62.5
## What's Changed
## 🐛 Bug Fixes
- fix: prevent Boolean toggle from being squashed by long descriptions @Wiesenwischer (#376)
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.62.4...v0.62.5
## 🐛 Bug Fixes
- fix: prevent Boolean toggle from being squashed by long descriptions @Wiesenwischer (#376)
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.62.4...v0.62.5
v0.62.4 – ProductDeployment stuck-recoveryv0.62.4
## What's Changed
## 🐛 Bug Fixes
- fix: recover stuck ProductDeployment in Deploying/Upgrading/Redeploying (#374) @Wiesenwischer (#375)
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.62.3...v0.62.4
## 🐛 Bug Fixes
- fix: recover stuck ProductDeployment in Deploying/Upgrading/Redeploying (#374) @Wiesenwischer (#375)
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.62.3...v0.62.4
v0.62.3 – Configurable init-container timeoutv0.62.3
## What's Changed in v0.62.3
- Configurable init-container timeout per service (#373)
- Configurable init-container timeout per service (#373)
v0.62.2 – Health Dashboard Performance Hotfixv0.62.2
## What's Changed in v0.62.2
- Fix slow health summary endpoint (#369)
- Fix slow health summary endpoint (#369)
v0.62.1 – Maintenance Observer Bugfixv0.62.1
## What's Changed
## 🐛 Bug Fixes
- Fix: wire maintenance observer config onto ProductDeployment @Wiesenwischer (#365)
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.62.0...v0.62.1
## 🐛 Bug Fixes
- Fix: wire maintenance observer config onto ProductDeployment @Wiesenwischer (#365)
**Full Changelog**: https://github.com/Wiesenwischer/ReadyStackGo/compare/v0.62.0...v0.62.1
v0.62.0 – EF Core migrations + legacy database baseline detectionv0.62.0
## What's Changed in v0.62.0
No issues found in this milestone.
No issues found in this milestone.
v0.61.0 – OCI Stack Bundles + Port Conflict Bugfixv0.61.0
## What's Changed in v0.61.0
- OCI Stack Bundles (#285)
- OCI Stack Bundles (#285)
v0.59.0 – Deployment Precheckv0.59.0
## What's Changed in v0.59.0
- Add Product Deployment Precheck (#356)
- Add Deployment Precheck feature (#354)
- Add Product Deployment Precheck (#356)
- Add Deployment Precheck feature (#354)
v0.60.0 – Complete Health Check Support — TCP probing, Docker HEALTHCHECK passthrough, container creation health configv0.60.0
## What's Changed in v0.60.0
- Complete Health Check Support (#351) (#360)
- Add TCP health check and Docker HEALTHCHECK passthrough (#359)
- Complete Health Check Support — TCP, Docker HEALTHCHECK, Container Creation (#351)
- Complete Health Check Support (#351) (#360)
- Add TCP health check and Docker HEALTHCHECK passthrough (#359)
- Complete Health Check Support — TCP, Docker HEALTHCHECK, Container Creation (#351)
Roadmap
Section titled “Roadmap”Planned features for future versions: