Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update only specified dependency (cli argument for updates.allow?) #1470

Closed
MPV opened this issue Jun 5, 2020 · 4 comments · Fixed by #1483
Closed

Update only specified dependency (cli argument for updates.allow?) #1470

MPV opened this issue Jun 5, 2020 · 4 comments · Fixed by #1483

Comments

@MPV
Copy link

MPV commented Jun 5, 2020

What

Could Scala Steward create pull-requests for only a specific dependency (across multiple downstream repositories)?

Why?

If a dependency (in our case, an internal private library) is updated, we'd like to get create pull requests for this library (and only that) in downstream consumers of this library.

What I've tried:

We use Scala Steward through the scala-steward-action, so it would be helpful to be able to pass this as a CLI argument.

Just setting updates.allow in .scala-steward.conf wouldn't help since Scala Steward checks out the repos itself, where I can't modify that file locally per runthrough.

Notes

I understand that changing this would be a bit of a shift in which purpose Scala Steward fulfills,
from:
update all dependencies in this/these repos (consumer-centric)
into:
update this dependency in all my consumers (producer/dependency-centric)

Curious to hear your thoughts on this.

@fthomas
Copy link
Member

fthomas commented Jun 16, 2020

@mzuehlke noted that #1483 could solve this issue and I agree with Marco that it looks like a nice solution for this request. What do you think, @MPV?

@MPV
Copy link
Author

MPV commented Jun 17, 2020

Looks great, thanks @mzuehlke & @fthomas!

@fthomas fthomas linked a pull request Jun 17, 2020 that will close this issue
@ches
Copy link

ches commented Jun 17, 2020

Part of our use case for #1483 is pretty much the same, it'd be good perhaps to give it as motivation on the PR but I'll echo it here as also a testimonial ☺️

We have a number of common libraries within the organization that are widely adopted. In order to help a small number of volunteer maintainers support them, Scala Steward keeps our little private ecosystem moving forward.

With downstream consumers that are application projects with large dependency graphs, though, the full firehose of Maven Central updates is too much churn and risk for most app teams to tolerate day-to-day. We're aiming to run an instance of Steward scoped to updating our blessed libraries, which is hopefully much easier to opt into and even mandate.

Steward can bring us a little closer to library upkeep benefits of a monorepo, without a monorepo.

@fthomas
Copy link
Member

fthomas commented Jun 17, 2020

Thanks for sharing your motivation for #1483, @ches, that's very helpful!

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 a pull request may close this issue.

3 participants