CHANGELOG
Ce qu'on a
livré.
Chaque feature, fix et amélioration apportés à FerrVault. Vue cross-produit sur ferrlabs.com/changelog.
RSSFerrVault API: defence-in-depth headers on every response, not just the ones nginx fronts
Direct callers of api.ferrvault.com received no security response headers at all. The CLI, the Kubernetes operator and anything using curl now get the same set the web app already had. HSTS is opt-in via a new FERRVAULT_TLS_ENABLED setting.
FerrVault operator: refreshInterval now actually governs how often secrets are pulled
Both controllers reconciled continuously instead of on their configured interval, so every FerrVaultSecret was reading from the API in a tight loop. The setting is now honoured. Expect a sharp drop in API calls and audit events from your clusters.
FerrVault: API package shipped to GHCR for the first time
ferrvault-api is now a proper independently-versioned package with its own Docker image and FerrFlow release lane. End of the "API lives in the app repo but never gets built" era.
FerrVault: End-to-end backend rewrite. Every screen talks to a real endpoint
Mocks are gone. Vault edit/delete, secret version history, and the K8s operator token page now hit real APIs. Sidebar trimmed to the three surfaces that actually have a data model.