Tag-mapped environments, access-control hardening & a richer activity feed
Map git tags to environments so Fireweave knows where every change landed, benefit from a dedicated access-control hardening pass, and follow integration activity in a richer feed.
Tag-based environment mapping
Map git refs and tags to environments and Fireweave attributes every deploy to the right place automatically — a v1.2.3 tag lands in production, a staging tag lands in staging, no manual bookkeeping.
Access-control hardening
A dedicated security pass tightened authorization across project and organization APIs and aligned role-based permissions between the API and the UI. Every project- and membership-scoped call is now authorization-checked end to end.
A richer integration activity feed
The integrations activity feed now shows what actually happened — installs, syncs, credential events — as first-class rows you can scan, instead of a flat log.
Improved
- Observability export is vendor-swappable over OTLP — point Fireweave’s signals at the backend you already run
- Marketplace: installed integrations show their semantic version instead of a deploy SHA
- Rollouts awaiting a deploy now show how long they’ve been waiting and what to do next
- Member avatars show first and last initials
Fixed
- Ramps reload the rollout’s environment before writing flag changes, so promotions always target the right environment
- Account recovery and multi-environment seal edge cases in the rollout live path