Skip to content

Move to the 2026 dependency baseline - #431

Merged
ChristopherDavenport merged 5 commits into
mainfrom
baseline-2026
Sep 26, 2026
Merged

ChristopherDavenport merged 5 commits into
mainfrom
baseline-2026

Conversation

@ChristopherDavenport

Copy link
Copy Markdown
Collaborator

Moves this repo to the org's 2026 dependency baseline.

Scala 2.13.18, 3.3.8 LTS — 2.12 dropped
Scala.js / Native 1.22.0 / 0.5.12
cats / cats-effect / fs2 2.13.0 / 3.7.1 / 3.14.0
http4s 0.23.37
log4cats 2.8.0
test stack munit 1.3.1, munit-cats-effect 2.2.1, scalacheck 1.20.0, discipline-munit 2.0.0

Why now. fs2 and http4s are the drivers: every repo in the org sat below the fs2 3.12.2 advisory floor and thirteen below the 3.2.11 one, with fourteen below http4s 0.23.17. The Typelevel stack moves together, so clearing those meant moving the rest.

Why a minor and not a patch. Dropping Scala 2.12 and moving Scala Native 0.4 → 0.5 are both breaking for consumers.

Validated locally across the org by cross-building and publishLocal-ing each dependency layer in turn. No source incompatibility with cats-effect 3.7, Scala 3.3.8 or Native 0.5 was found in any repo; where a source change appears it is the removal of epollcat, whose Native IOApp cats-effect 3.6 absorbed.

🤖 Generated with Claude Code

Scala 2.13.18 and 3.3.8 LTS, dropping 2.12. cats 2.13.0, cats-effect 3.7.1,
fs2 3.14.0, http4s 0.23.37, log4cats 2.8.0, and the munit/scalacheck/scodec
test stack brought current. Scala.js 1.22.0 and Scala Native 0.5.12.

fs2 and http4s are the reason this is not optional: every repo sat below the
fs2 3.12.2 floor, thirteen below the 3.2.11 one, and fourteen below http4s
0.23.17. The rest follows because the Typelevel stack moves together.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The baseline drops Scala 2.12 and moves Scala Native from 0.4 to 0.5, both of
which are breaking for consumers, so this is not a patch release.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@mergify

mergify Bot commented Sep 26, 2026 •

Copy link
Copy Markdown
Contributor

This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again.

Dropping Scala 2.12 changes the generated CI matrix, so the committed
workflow no longer matched the build and githubWorkflowCheck failed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@ChristopherDavenport

Copy link
Copy Markdown
Collaborator Author

Parked behind davenverse/circuit#316 — needs circuit_native0.5 to exist. Branch kept.

fommil and others added 2 commits September 26, 2026 10:28
Picks up the 2026 baseline plus three fixes: the Scala Native reset-boundary
timeout, NoStackTrace on RejectedExecution, and the premature-close fix for
davenverse/circuit#301.

The previous commit is the client-side half of that NoStackTrace change, so the
two throwables in CircuitedClient no longer disagree.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@ChristopherDavenport

Copy link
Copy Markdown
Collaborator Author

Reopened now that circuit 0.7.0 is on Central.

This branch now carries two things:

  1. @fommil's no stack traces for the default rejected translation impl #428 — cherry-picked with authorship intact, so that PR can close as merged-via-this-one. It is the client-side half of the NoStackTrace change; circuit got the other half in Update fs2-io to 3.1.5 #313. Before it, the two throwables in CircuitedClient disagreed — CircuitedClientResourceThrowable already had NoStackTrace while RejectedExecutionHttp4sClient did not.

  2. circuit 0.5.1 → 0.7.0, which brings the 2026 baseline plus three fixes: the Scala Native reset-boundary timeout, NoStackTrace on RejectedExecution, and the premature-close fix for premature closing? circuit#301.

Verified locally against the released circuit 0.7.0 on 2.13 and 3 — 4 tests passing on each.

🤖 Generated with Claude Code

@ChristopherDavenport
ChristopherDavenport merged commit fc6b223 into main Sep 26, 2026
19 checks passed
@ChristopherDavenport
ChristopherDavenport deleted the baseline-2026 branch September 26, 2026 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants