v0.1.4: Restart on a failed startup

A database blip while the portal was starting used to leave it running and serving nothing, which cost nearly three hours of downtime. Startup now ends the process when a plugin cannot come up, so the pod restarts instead of sitting dead, and liveness fails once the backend has never reached ready inside its deadline.

A short database absence no longer costs a restart. Each retry opens a fresh connection, so a database that returns within thirty seconds is waited out rather than failed.

What's Changed

• fix: Restart Backstage when startup fails to reach ready by @ecv in #82

Full Changelog: v0.1.3...v0.1.4

v0.1.3: Backstage 1.54.7

Backstage moves from 1.52.0 to 1.54.7, the first upstream update to reach the portal since the weekly bump opened pull requests that no check ever ran on. The portal's own catalog entry now names a real owning team instead of the scaffolder placeholder.

What's Changed

• chore: bump Backstage to latest release by @app/github-actions in #79
• fix: replace scaffold owner in root catalog-info by @ecv in #76

Full Changelog: v0.1.2...v0.1.3

v0.1.2

The service catalog now says Service and Team in its interface, matching the words the rest of the platform uses. The weekly Backstage update can open its pull request again, and dependency updates move to the shared Renovate policy.

What's Changed

• feat: Say Service and Team in the catalog UI by @ecv in #63
• chore: swap Dependabot for Renovate on the shared policy by @ecv in #64
• chore: remove dead Snyk scan workflow by @ecv in #75
• fix: Let the weekly bump write its own lockfile by @ecv in #78

Full Changelog: v0.1.1...v0.1.2

v0.1.1

What's Changed

• fix: move Namespace out of base into opt-in component by @ecv in #26

New Contributors

• @ecv made their first contribution in #26

Full Changelog: v0.1.0...v0.1.1

v0.1.0

First tagged release of the Datum Backstage portal. Publishes the stable ghcr.io/datum-cloud/backstage-kustomize:v0.1.0 bundle (signed + attested) for production to pin.