You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When CompatHelper is used for subdirs, e.g. docs or eventual examples, one wants to use the latest commit version of the current PR or of master/main from the parent repo/package.
Therefore putting a compat for the parent package does not makes sense. A solution would be to pass a list of packages to ignore when running CompatHelper.jl, maybe a blacklist keyword?
The text was updated successfully, but these errors were encountered:
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.
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:
use a 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
do not open a PR if the version is specified in the form < 0.3
do not open the PR if there's a similar one (either open or closed)
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 a
compat
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?The text was updated successfully, but these errors were encountered: