Skip to content

Update fs2-core to 3.15.0 - #1219

Merged
mergify[bot] merged 2 commits into
profunktor:masterfrom
scala-steward:update/fs2-core-3.15.0
Nov 19, 2026
Merged

mergify[bot] merged 2 commits into
profunktor:masterfrom
scala-steward:update/fs2-core-3.15.0

Conversation

@scala-steward

Copy link
Copy Markdown
Contributor

About this PR

📦 Updates co.fs2:fs2-core from 3.14.0 to 3.15.0

📜 GitHub Release Notes - Version Diff

Usage

✅ Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "co.fs2", artifactId = "fs2-core" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "co.fs2", artifactId = "fs2-core" }
}]
labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

@mergify

mergify Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

This pull request is merged.

Comment thread project/Dependencies.scala Resolved
@matejcerny
matejcerny force-pushed the update/fs2-core-3.15.0 branch from 85cc44c to 977888a Compare November 19, 2026 09:36
@mergify
mergify Bot merged commit 977888a into profunktor:master Nov 19, 2026
3 checks passed
@mergify

mergify Bot commented Nov 19, 2026

Copy link
Copy Markdown
Contributor

This pull request, with head sha 977888a390bbcaa47b158a7e9bccc8697d3629bd, has been successfully merged with fast-forward by Mergify.

This pull request will be automatically closed by GitHub.

As soon as GitHub detects that the sha 977888a390bbcaa47b158a7e9bccc8697d3629bd is part of the master branch, it will mark this pull request as merged.

It is possible for this pull request to remain open if this detection does not happen, this usually happens when a force-push is done on this branch update/fs2-core-3.15.0, this means GitHub will fail to detect the merge.

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