Sounds like there are no objections, and some additional good reasons I
didn't mention to use this tool. I'll make the pull request to add
apache/daffodil as a repo for Scala Steward to track.
I'd recommend creating a ticket for any updates you think would be
useful, such as the versioning scheme.
P.S. I've been meaning to pass along another useful Scala ecosystem article I
read recently [1]. Library writers are being asked to define a `ThisBuild /
versionScheme` setting to declare a library's semantic versioning scheme (like
Daffodil's in our case) so that sbt can issue more reliable (
I like the idea of using the Scala Stewart bot to keep Daffodil's library
dependencies and sbt plugins up-to-date very much. In fact, I noticed two more
benefits you didn't mention due to a significant part of the Scala ecosystem
already using the Scala Stewart bot:
[1]
https://github.com/sca
There's been this increase of software supply chain hacks these days.
Since this bot is on our ongoing development branch, and so long as we watch
these changes and verify the dependencies it chooses before merging these PRs,
then this makes this version updating an incremental effort done as th
