-
Notifications
You must be signed in to change notification settings - Fork 502
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
Support reading a default repo config from this repository #2337
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2337 +/- ##
==========================================
+ Coverage 79.71% 80.19% +0.48%
==========================================
Files 137 138 +1
Lines 2406 2404 -2
Branches 56 57 +1
==========================================
+ Hits 1918 1928 +10
+ Misses 488 476 -12
Continue to review full report at Codecov.
|
Is there a way to disable fetching default configuration from github? With on-prem & firewall rules new version can't be run |
@eugeniyk Yes, with |
ah ok, thanks! |
We're already seeing Scala Steward raise PRs for Scala 3.4.0, this might be unintentional? guardian/play-secret-rotation#432 See also scala-steward-org#2337 & scala-steward-org#1104
We're already seeing Scala Steward raise PRs for Scala 3.4.0, this might be unintentional? guardian/play-secret-rotation#432 See also #2337 & #1104
This adds support for reading a defaultl repo config from this repository. Multiple repo configs can be loaded per Scala Steward installation with the
--repo-config
command-line option and are merged into one effective global repo config. Loading the default repo config from this repository can be disabled with--disable-default-repo-config
. This is similar to the handling of Scalafix and artifact migrations config files.The purpose of this change is to allow library maintainers to tell Scala Steward to ignore updates until a new version is announced (#1104). They can do this by adding new entries to the
updates.ignore
list of the default repo config. All (public and private) Scala Steward installations that do not opt-out of loading the default repo config will then ignore the added updates until the default repo config is changed again.The default repo config also contains ignored updates that were previously removed by
FilterAlg.removeBadVersions
. So this function was just a defaultupdates.ignore
list in disguise.Note also that this is a breaking change for users that are using the old
--default-repo-conf
option.--repo-config
is a drop-in replacement for that option.