You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs(upgrade): no migration notes for 0.1.1, 0.1.2, or 0.1.3 (only the 0.1.0 page exists) #4398
The docs/upgrade/ directory contains only 0-1-0.mdx. Three GA releases have shipped since (0.1.1, 0.1.2, 0.1.3) with no upgrade or migration page for any of them. A reader running 0.1.1 or later has no way to tell whether the 0.1.0 guidance still applies or what changed in their jump.
This matters most for 0.1.3, which is not a pure patch release. From the release notes it includes operator-affecting changes with no migration guidance:
By contrast, 0.1.1 and 0.1.2 look like patch releases (fixes, docs, perf), with only minor behavior changes in 0.1.1 (WebSocket tunnel made opt-in, snap gateway mTLS). If that is correct, even a one-line "no migration steps beyond 0.1.0" note would close the gap for those two.
Request
Add upgrade notes for 0.1.1, 0.1.2, and 0.1.3, even where the entry is simply "no action needed," and state which parts of the 0.1.0 guide still apply.
To prevent recurrence, consider making an "upgrade impact / migration steps" entry a standard part of the release checklist, so each release either links a docs/upgrade/ page or explicitly records that no migration is required. You already publish detailed GitHub release notes (see docs: describe 0.1 series in release callouts #3732); this would add a short upgrade-impact callout rather than a new process.
Found while writing operator upgrade guidance for a downstream consumer (Red Hat Agentic Starter Kits guide) pinned at 0.1.2.
The
docs/upgrade/directory contains only0-1-0.mdx. Three GA releases have shipped since (0.1.1, 0.1.2, 0.1.3) with no upgrade or migration page for any of them. A reader running 0.1.1 or later has no way to tell whether the 0.1.0 guidance still applies or what changed in their jump.This matters most for 0.1.3, which is not a pure patch release. From the release notes it includes operator-affecting changes with no migration guidance:
feat(helm): make cluster-scoped RBAC optional(feat(helm): make cluster-scoped RBAC optional #3459) — changes the RBAC an operator installs.fix(network): refuse protocol upgrades on JSON-RPC and MCP endpoints(fix(network): refuse protocol upgrades on JSON-RPC and MCP endpoints #3753) and the GraphQL equivalent (fix(network): refuse protocol upgrades on GraphQL endpoints #3841) — can break clients that relied on protocol upgrades.feat(sandbox): add main restart policy(feat(sandbox): add main restart policy #2798) — changes sandbox restart behavior.By contrast, 0.1.1 and 0.1.2 look like patch releases (fixes, docs, perf), with only minor behavior changes in 0.1.1 (WebSocket tunnel made opt-in, snap gateway mTLS). If that is correct, even a one-line "no migration steps beyond 0.1.0" note would close the gap for those two.
Request
docs/upgrade/page or explicitly records that no migration is required. You already publish detailed GitHub release notes (see docs: describe 0.1 series in release callouts #3732); this would add a short upgrade-impact callout rather than a new process.Found while writing operator upgrade guidance for a downstream consumer (Red Hat Agentic Starter Kits guide) pinned at 0.1.2.