Open theogf opened 2 years ago
As a short-term workaround, if you put a compat entry of the form e.g.
[compat]
Foo = ">= 1.2.3"
Then CompatHelper won't make any PRs to modify the compat entry for Foo
.
My problem is that I would like to not put any compact so that the GH actions for creating the docs and other things use the dev version of the package.
a blacklist
keyword would indeed be nice.
The propoesd workaround does not set an uper-bound and hence would not work if I don't want to support a new breaking version of a dependency (for lack of bandwidth to upgrade or other reasons).
A few options off the top of my head:
blacklist
keyword an support a compat-settings.yml
file that can be put in the the repository to pass the list of blacklisted packages to CompatHelper.jl
< 0.3
When CompatHelper is used for subdirs, e.g.
docs
or eventualexamples
, one wants to use the latest commit version of the current PR or of master/main from the parent repo/package. Therefore putting acompat
for the parent package does not makes sense. A solution would be to pass a list of packages to ignore when runningCompatHelper.jl
, maybe ablacklist
keyword?