FDN-4458 Flow dependency updates

[team-foundation-git]

About this PR

Updates:

• 📦 io.flow:sbt-flow-linter from 0.0.77 to 0.0.78

Usage

✅ Please merge!

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

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 these to your .scala-steward.conf file to ignore future updates of these dependencies:

updates.ignore = [
  { groupId = "io.flow", artifactId = "sbt-flow-linter" }
]

Or, add these to slow down future updates of these dependencies:

dependencyOverrides = [
  {
    pullRequests = { frequency = "30 days" },
    dependency = { groupId = "io.flow", artifactId = "sbt-flow-linter" }
  }
]

^{labels: scala-steward, auto-merge}

Summary by CodeRabbit

• Chores
  • Updated development dependencies to latest versions.

[coderabbitai]

📝 Walkthrough

Walkthrough

The change bumps the sbt-flow-linter plugin from version 0.0.77 to 0.0.78 in the project build configuration. This is a minor version increment for a development tool plugin with no structural or functional changes to the codebase.

Changes

Cohort / File(s)	Summary
Plugin version bump project/plugins.sbt	Bumps io.flow:sbt-flow-linter from 0.0.77 to 0.0.78

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• FDN-4458 Flow dependency updates #273: Bumps io.flow:sbt-flow-linter from 0.0.76 to 0.0.77 in the same file, consecutive version update.
• FDN-4404 Flow dependency updates #271: Updates io.flow:sbt-flow-linter version with sequential version increment in project/plugins.sbt.
• FDN-4404 Flow dependency updates #269: Modifies the same plugin declaration to bump io.flow:sbt-flow-linter version.

Suggested reviewers

• jackl

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'FDN-4458 Flow dependency updates' accurately describes the main change: updating a Flow dependency (sbt-flow-linter plugin) in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[flow-tech]

Click here for code coverage report: https://jenkins.flo.pub/job/flowcommerce/job/lib-util/job/PR-276/1/scoverage-report/

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@project/plugins.sbt`:
- Line 4: The addSbtPlugin line for sbt-flow-linter uses coordinates
addSbtPlugin("io.flow" % "sbt-flow-linter" % "0.0.78") which cannot be resolved;
either verify and correct the plugin coordinates (groupId/artifactId/version) to
the published sbt plugin, or if this is an internal plugin add the appropriate
resolver entry (e.g., a private Ivy/Maven resolver) to plugins.sbt so sbt can
fetch it, or replace the plugin with the correct published artifact (or move it
to libraryDependencies if it's a library, not an sbt plugin).

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

sbt-flow-linter 0.0.78 release notes

💡 Result:

I couldn’t find any public “release notes”/changelog entry for sbt-flow-linter version 0.0.78 via web search (no GitHub Releases page, tag v0.0.78, Scaladex entry, or Maven Central page turned up under that name).

If you share one of the following, I can pull the exact notes:

• the GitHub repo URL, or
• the Maven/Ivy coordinates (groupId + artifactId), or
• a link to where you saw 0.0.78 published (e.g., an internal Nexus/Artifactory page).

---

🌐 Web query:

sbt-flow-linter io.flow maven central

💡 Result:

I couldn’t find any artifact named sbt-flow-linter with groupId io.flow on Maven Central (Sonatype Central / repo1.maven.org) based on multiple searches.

What I did find is that io.flow publishes various artifacts that show up under a separate repository named “Flow” on MvnRepository (i.e., not “Central”), for example io.flow:spdf and io.flow:lib-harmonization-play26_2.12. [1], [2]

If you share either:

• the plugin’s GitHub repo, or
• the exact sbt line you were told to add (e.g., addSbtPlugin(...)),
  I can identify the correct coordinates/repository (or confirm it isn’t published).

Sources: [1] (mvnrepository.com) [2] (mvnrepository.com)

Citations:

• 1: https://mvnrepository.com/artifact/io.flow/spdf?utm_source=openai
• 2: https://mvnrepository.com/artifact/io.flow/lib-harmonization-play26_2.12/0.0.79?utm_source=openai

---

🌐 Web query:

sbt-flow-linter GitHub plugin

💡 Result:

I couldn’t find any GitHub repo or sbt plugin specifically named sbt-flow-linter via web search.

The closest match to “flow-linter” + “plugin” is CoreKraft’s Flow Linter, which is a Salesforce CLI (sf/sfdx) plugin published on npm as @corekraft/flow-linter, with its repo listed as corekraft/flow-linter-sfcli. [1]

If you meant an sbt (Scala) plugin, can you share:

• the GitHub org/user (if you know it), or
• a snippet of your project/plugins.sbt, or
• where you saw the name “sbt-flow-linter” (link/text)?

Sources
[1] npm package page for @corekraft/flow-linter (shows repo corekraft/flow-linter-sfcli) https://www.npmjs.com/package/@corekraft/flow-linter

---

🌐 Web query:

io.flow sbt plugin scala

💡 Result:

I couldn’t find an sbt plugin published under the Maven/Ivy group io.flow. What does show up under io.flow are regular Scala libraries (added with libraryDependencies, not addSbtPlugin)—e.g. lib-reference-scala and lib-cats-effect. [1], [2]

If you meant “use an io.flow Scala library from sbt”

Add it like this in build.sbt (example artifact/version):

libraryDependencies += "io.flow" %% "lib-reference-scala" % "0.3.84"

[1]

Some io.flow artifacts are hosted on Flow’s JFrog repository (per MvnRepository), so you may also need a resolver:

resolvers += "Flow" at "https://flow.jfrog.io/flow/libs-release/"

[2]

If you truly meant an sbt plugin

You’d normally use coordinates like:

addSbtPlugin("group.id" % "plugin-name" % "x.y.z")

and sbt plugins typically resolve to artifacts with suffixes like _2.12_1.0 on indexes such as Scaladex (Scala Index).

If you tell me the plugin name (or paste the error / the dependency line you tried), I can give you the exact addSbtPlugin(...) line and any required resolvers.

Sources: [1] [2]

---

Confirm plugin coordinates and repository availability—sbt-flow-linter cannot be resolved from public repositories.

Web searches found no published sbt-flow-linter with group io.flow in Maven Central, Scaladex, or GitHub. The io.flow group publishes Scala libraries (not sbt plugins), typically used with libraryDependencies in build.sbt, not addSbtPlugin in plugins.sbt.

Either:

• Verify the plugin coordinates are correct (groupId, artifactId, version)
• Add a resolver for a private/internal repository if this plugin is internal
• Confirm version 0.0.78 exists and is accessible from your configured resolvers

Without resolution configuration, the build will fail.

🤖 Prompt for AI Agents

In `@project/plugins.sbt` at line 4, The addSbtPlugin line for sbt-flow-linter
uses coordinates addSbtPlugin("io.flow" % "sbt-flow-linter" % "0.0.78") which
cannot be resolved; either verify and correct the plugin coordinates
(groupId/artifactId/version) to the published sbt plugin, or if this is an
internal plugin add the appropriate resolver entry (e.g., a private Ivy/Maven
resolver) to plugins.sbt so sbt can fetch it, or replace the plugin with the
correct published artifact (or move it to libraryDependencies if it's a library,
not an sbt plugin).