# Critical Release Datomic 1.0.7469 Pro now Available

**URL:** <https://forum.datomic.com/t/critical-release-datomic-1-0-7469-pro-now-available/2598>\
**Category:** Announcements\
**Created:** [October 23, 2025, 5:38pm UTC](https://forum.datomic.com/t/critical-release-datomic-1-0-7469-pro-now-available/2598 "2025-10-23T17:38:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jaret](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.datomic.com/jaret/32/45_2.png) [@jaret](https://forum.datomic.com/u/jaret)\
**Post date:** [October 23, 2025, 5:38pm UTC](https://forum.datomic.com/t/critical-release-datomic-1-0-7469-pro-now-available/2598/1 "2025-10-23T17:38:03Z")

</div>

This message covers changes in this release. The complete change log can be found at [Change Log | Datomic](https://docs.datomic.com/changes/pro.html). To download this release see [Datomic Pro Releases | Datomic](https://docs.datomic.com/releases-pro.html).

For a summary of critical release notices, see [Release Notices | Datomic](http://docs.datomic.com/release-notices.html)

## 1.0.7469: 2025/10/23

- Fix: Indexing slowly leaks garbage segments in storage which are unrecoverable by `gc-storage`.
- Fix: excisions may not be completely applied to [as-of](https://docs.datomic.com/clojure/index.html#datomic.api/as-of) or [history](https://docs.datomic.com/clojure/index.html#datomic.api/history) database values

Datomic Release 1.0.7469 fixes a bug that prevented excisions from removing datoms from the [as-of](https://docs.datomic.com/clojure/index.html#datomic.api/as-of) or [history](https://docs.datomic.com/clojure/index.html#datomic.api/history) indexes. This release also includes a tool to detect incomplete excisions to the index and optionally re-apply them. This bug only affects databases that contain excision datoms (`:db/excise`). This bug does not affect ordinary database values (those without [as-of](https://docs.datomic.com/clojure/index.html#datomic.api/as-of) or [history](https://docs.datomic.com/clojure/index.html#datomic.api/history)), nor the transaction log.

See: [Excision Repair Tool](https://docs.datomic.com/release-notices.html#excision-repair-tool)

The tool works in both report and repair modes while the transactor runs. The tool needs read permissions to storage, like a peer. Repair mode requires write permissions.

---

<div class="post-metadata">

**Author:** ![jaret](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.datomic.com/jaret/32/45_2.png) [@jaret](https://forum.datomic.com/u/jaret)\
**Post date:** [October 24, 2025, 5:48pm UTC](https://forum.datomic.com/t/critical-release-datomic-1-0-7469-pro-now-available/2598/2 "2025-10-24T17:48:09Z")

</div>

I wanted to publicly thank Mykola Androsovych and the rest of the folks at [Viax.io](http://Viax.io).

Mykola’s company is [viax.io](https://viax.io/) and they use Datomic as the foundation for their entire data persistence layer, building a GraphQL abstraction over it. Mykola reported, identified and reproduced the excision bug and was able to supply our team everything we needed to address what would have otherwise been a very subtle and difficult bug to capture. Thanks Mykola!