---
title: "Release v0.7.0 · fuelen/composite"
url: https://daily.dev/posts/release-v0-7-0-fuelen-composite-yrw1mbzij
source_url: https://github.com/fuelen/composite/releases/tag/v0.7.0
type: article
source: "ElixirStatus"
published: 2026-08-22T18:18:45.987Z
updated: 2026-08-22T18:19:05.308Z
tags: ["elixir", "ecto"]
reading_time: 2
upvotes: 0
comments: 0
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Release v0.7.0 · fuelen/composite

**[ElixirStatus](https://daily.dev/sources/elixirstatus)** · 2 min read · 0 upvotes · 0 comments

## Summary

Composite v0.7.0 adds apply_tagged/1 and apply_tagged/3 functions that return :unchanged or {:changed, query} so callers can skip passing unchanged queries to Repo.all/1. The minimum Elixir version requirement is raised from ~> 1.9 to ~> 1.14 to match Ecto's minimum. Dependency ordering now respects :requires instead of an unordered MapSet, duplicate dependency declarations emit a warning, and several strict: true crashes involving nested nil parameters are fixed. Internal changes include an O(n·m) to amortized O(n) refactor and new CI on Elixir 1.14/1.19.4.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://github.com/fuelen/composite/releases/tag/v0.7.0>

## Questions this post answers

### What is the minimum Elixir version required by Composite v0.7.0?

Composite v0.7.0 requires Elixir ~> 1.14 as its minimum version, up from ~> 1.9 in earlier releases. This change was made to match Ecto's own minimum Elixir version requirement, meaning projects on older Elixir versions must upgrade before adopting this release.

_daily.dev helps developers track dependency version bumps like this before they break a build._

### How do I avoid passing an unchanged Ecto query to Repo.all/1 when using Composite?

Use the new Composite.apply_tagged/1 or apply_tagged/3 functions introduced in version 0.7.0, which return :unchanged when the resulting query compares equal (==) to the input, or {:changed, query} otherwise. This lets calling code short-circuit and skip an unnecessary Repo.all/1 call on an unmodified query.

_Elixir developers optimizing Ecto query pipelines can follow library updates like this on daily.dev._

### Why did dependency loading order change in Composite's dependency/4 macro?

The previous MapSet-based implementation for handling dependency/4 declarations did not preserve declaration order, so dependencies could load out of sequence. Version 0.7.0 fixes this so dependencies now load in the order specified by :requires, and declaring the same dependency name twice emits an IO.warn/1 message while still overwriting the previous loader.

_daily.dev keeps developers current on library fixes that change dependency behavior like this._

## Similar posts on daily.dev

- [Elixir v1.20.0-rc.2 released](https://daily.dev/posts/elixir-v1-20-0-rc-2-released-vo8dwwpw4) · Elixir Forum · 1 upvotes · 0 comments

---

Tags: [#elixir](https://daily.dev/tags/elixir), [#ecto](https://daily.dev/tags/ecto)

[View this post on daily.dev](https://daily.dev/posts/release-v0-7-0-fuelen-composite-yrw1mbzij)