FOSSA CLI
fossa-cli's feed jumps from 3.17 to 3.20, with clearer container scan errors.
A side-by-side editorial comparison of NetBox and Terragrunt — release velocity, themes, recent moves, and the top alternatives to consider.
NetBox 4.7's patch run fixes a token leak and a broken restore path.
Four 4.7 patches followed the September 4.7.0 release. 4.7.1 reinstalled hierarchical-path triggers that a pg_dump restore silently dropped, 4.7.2 stopped background bulk requests recording plaintext API tokens in job results, 4.7.3 was a REST and GraphQL performance release, and 4.7.4 adds change-log IDs to webhook payloads, fixes the circuit status GraphQL enum and warns about a thumbnail storage change.
Terragrunt 1.2's last candidate finishes eleven experiments and locks down state buckets.
Terragrunt v1.2.0-rc3, dated mid-October, is declared the final candidate: unless a blocker appears, v1.2.0 ships with its contents. The cycle completes eleven experiments, among them OCI, block-iteration, azure-backend and optional-hooks. Two changes need attention: base64gzip() now returns the Go 1.27 encoder's output, which can trigger resource replacements, and S3 bootstrapping no longer adds the RootAccess bucket policy statement.
Four 4.7 patches followed the September 4.7.0 release. 4.7.1 reinstalled hierarchical-path triggers that a pg_dump restore silently dropped, 4.7.2 stopped background bulk requests recording plaintext API tokens in job results, 4.7.3 was a REST and GraphQL performance release, and 4.7.4 adds change-log IDs to webhook payloads, fixes the circuit status GraphQL enum and warns about a thumbnail storage change.
The ltree migration in 4.7.0 is still generating follow-up work, and the patch notes are candid about what broke. Performance work on REST serialisation and GraphQL has been steady across the line, and event payloads are getting richer for automation users.
Expect further 4.7.x patches on a two-week rhythm with more API performance fixes; the entries don't show what 4.8 will contain.
Terragrunt v1.2.0-rc3, dated mid-October, is declared the final candidate: unless a blocker appears, v1.2.0 ships with its contents. The cycle completes eleven experiments, among them OCI, block-iteration, azure-backend and optional-hooks. Two changes need attention: base64gzip() now returns the Go 1.27 encoder's output, which can trigger resource replacements, and S3 bootstrapping no longer adds the RootAccess bucket policy statement.
The graduation model has repeated at a larger scale: six experiments in v1.1, eleven in v1.2. The candidates ran as stabilization, with fixes concentrated in the CAS, the catalog and the Provider Cache Server. Each breaking change also ships with an escape hatch, base64gzip_compat() or enable_bucket_root_access, which shows how seriously the project treats its 1.0 guarantees.
v1.2.0 final is the next release, since rc3 says only regression or urgent fixes will land first. It has not appeared in this feed in the 18 days since rc3.
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either NetBox or Terragrunt.
fossa-cli's feed jumps from 3.17 to 3.20, with clearer container scan errors.
Gloo Gateway's October batch fixes proxies that silently kept stale endpoints.
Traefik v3.8 rc.1 is a Gateway API release; v2.11 keeps getting security patches.
Render's autumn changelog is plan tuning and runtime defaults while Workflows fills out.
Home Assistant keeps pulling hidden power-user features into the UI, now trigger IDs.
Alertmanager 0.34.2 turns off CORS by default, breaking cross-origin API calls.
See all NetBox alternatives → · See all Terragrunt alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. NetBox and Terragrunt are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. NetBox and Terragrunt are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top NetBox alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "NetBox alternatives" section above for the current picks, or visit /alternatives/netbox for the full list with editorial commentary on each.
Top Terragrunt alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Terragrunt alternatives" section above for the current picks, or visit /alternatives/terragrunt for the full list with editorial commentary on each.