By Category

Developer Portal

Back to all categories

Developer Portal

Jun 10, 2026 Developer Portal backstage v0.133.2
Changed
- App: migrate the Clusters, Deployments, Installations, Catalog, and Flux pages to the new frontend system page header. The Flux page’s list and tree views are now header tabs (/flux redirects to /flux/list), and the catalog page title is now just “Catalog” (overridable via app-config).
- App: migrate the Grafana plugin to the actively maintained @backstage-community/plugin-grafana — a drop-in replacement with no behavior change.
Fixed
- Auth: the MCP OAuth2 authenticator now sends the RFC 8707 resource parameter in authorization and token requests when a resource option is configured on an mcp-* auth provider, so issued access tokens are audience-bound to the target MCP server. This fixes the AI chat losing access to MCP servers fronted by JWT-validating gateways that reject tokens without the expected aud claim. See ./docs/releases/v0.133.2-changelog.md for more information.
Jun 9, 2026 Developer Portal happa v1.72.4
What’s Changed
Changes
- fix(footer): guard against undefined metadata version by @marians in https://github.com/giantswarm/happa/pull/4803
Full Changelog: https://github.com/giantswarm/happa/compare/v1.72.3...v1.72.4
Jun 8, 2026 Developer Portal happa v1.72.3
What’s Changed
Changes
- feat(analytics): track only authenticated pageviews via TelemetryDeck JS SDK by @marians in https://github.com/giantswarm/happa/pull/4800
Other Changes
- chore(deps): replace connected-react-router with redux-first-history by @marians in https://github.com/giantswarm/happa/pull/4750
- chore(ci): bump architect-orb to 8.0.2 by @marians in https://github.com/giantswarm/happa/pull/4738
- chore(deps): pin patched versions of vulnerable transitive deps by @marians in https://github.com/giantswarm/happa/pull/4742
- chore(deps): bump react-markdown to 9.1.0 and pin mdast-util-to-hast by @marians in https://github.com/giantswarm/happa/pull/4744
- chore(deps): bump @rjsf packages to 5.24.13 by @marians in https://github.com/giantswarm/happa/pull/4745
- chore(deps): remove validate.js (dead code) by @marians in https://github.com/giantswarm/happa/pull/4748
- feat(ci): add workflow to audit dependencies by @marians in https://github.com/giantswarm/happa/pull/4749
- fix(deps): pin form-data to ^4.0.4 via yarn resolution by @marians in https://github.com/giantswarm/happa/pull/4753
- fix(deps): pin ws to ^8.17.1 via yarn resolution by @marians in https://github.com/giantswarm/happa/pull/4754
- fix(renovate): remove schedule, increase concurrency by @marians in https://github.com/giantswarm/happa/pull/4755
- chore: align files according to platform standards in https://github.com/giantswarm/happa/pull/4799 https://github.com/giantswarm/happa/pull/4770 https://github.com/giantswarm/happa/pull/4714 https://github.com/giantswarm/happa/pull/4722 https://github.com/giantswarm/happa/pull/4802 https://github.com/giantswarm/happa/pull/4724
Full Changelog: https://github.com/giantswarm/happa/compare/v1.72.2...v1.72.3
Jun 3, 2026 Developer Portal backstage v0.133.1
Fixed
- AI chat: log “no OpenAI API key configured” at info instead of warn to reduce Sentry noise for customers who haven’t configured the feature.
- App: stop reporting “Untracked page view” warnings to Sentry for paths that don’t match any registered app route (e.g. bot/scanner probes like /wp-login.php). See ./docs/releases/v0.133.1-changelog.md for more information.
Jun 1, 2026 Developer Portal backstage v0.133.0
Added
- AI chat: add Opus 4.8 context window info.
Changed
- AI chat: make the Anthropic thinking config model-aware so adaptive-thinking Claude models (Opus 4.5+, Sonnet 4.6) use the adaptive thinking interface with a configurable effort (aiChat.anthropic.effort, default high), while older Claude models keep the legacy budget-based interface.
Fixed
- AI chat: forward chat-level errors to the error reporter (Sentry) so the “Network error” banner is no longer silent, and log a backend warning when the client disconnects mid-stream. See ./docs/releases/v0.133.0-changelog.md for more information.
May 20, 2026 Developer Portal backstage v0.132.1
Fixed
- AI chat: fix muster MCP connection by dropping the obsolete custom session-aware transport that broke against @modelcontextprotocol/sdk 1.29.0. Muster now uses the spec-standard Mcp-Session-Id header, which @ai-sdk/mcp’s built-in HTTP transport handles natively. See ./docs/releases/v0.132.1-changelog.md for more information.
May 19, 2026 Developer Portal backstage v0.132.0
Added
- Add LatestOciReleaseProcessor that annotates Component entities carrying giantswarm.io/helmcharts with giantswarm.io/latest-release-tag and giantswarm.io/latest-release-date from the referenced OCI registry. For multi-chart entities the highest-semver stable tag wins; prerelease tags are skipped. Toggle via catalog.processors.latestOciRelease.enabled.
Changed
- Introduce a new @giantswarm/backstage-plugin-gs-node node-library package and move the container-registry client code into it so it can be shared between gs-backend and the catalog module. Move parseChartRef from plugins/gs to gs-common so it can be used backend-side. See ./docs/releases/v0.132.0-changelog.md for more information.
May 14, 2026 Developer Portal backstage v0.131.1
Fixed
- Catalog: fall back to PAT or unauthenticated requests when the configured GitHub App has no access to a repo, so LatestReleaseProcessor and SbomDependencyProcessor work for repos outside the App’s installation (and public repos work without any integration configured).
- AI chat: pin the ai package to a single version via root yarn resolution to fix AI_TypeValidationError when invoking MCP tools. See ./docs/releases/v0.131.1-changelog.md for more information.
May 13, 2026 Developer Portal backstage v0.131.0
Added
- Add LatestReleaseProcessor that annotates Component entities with giantswarm.io/latest-release-tag and giantswarm.io/latest-release-date from GitHub Releases, with optional tag-prefix matching for monorepos.
- Add KlausProvider, a catalog entity provider that discovers Klaus personalities, toolchains, and plugins from GitHub and emits them as Component entities.
Fixed
- Fix Helm charts column in the catalog showing “Yes (0)” for entities without charts. See ./docs/releases/v0.131.0-changelog.md for more information.
May 11, 2026 Developer Portal backstage v0.130.0
Added
- PagerDuty integration: “Who is on call” entity card, catalog processor that auto-annotates entities with PagerDuty IDs, and MCP action to resolve PagerDuty IDs from catalog entities.
Changed
- Backstage liveness/readiness probe timings are now configurable via .Values.probes.{liveness,readiness} (initialDelaySeconds, periodSeconds, timeoutSeconds, failureThreshold) and the default timeoutSeconds is raised from the k8s implicit 1 to 5. The HTTP path/port stay fixed (/.backstage/health/v1/{liveness,readiness} on port). The k8s default 1s is tight against the chart’s 500m CPU limit: event-loop stalls during plugin startup, GC, or DB reconnects regularly miss the deadline and surface as Unhealthy: ... context deadline exceeded events even though the pod keeps serving traffic (observed on the BWI Backstage Deployment on spidertron, 2026-05-11). See ./docs/releases/v0.130.0-changelog.md for more information.