Add the force_latest_compatible_version input, and add the "auto-detect Dependabot/CompatHelper" functionality

[DilumAluthge]

This should not be merged until JuliaLang/Pkg.jl#2439 is merged.

[christopher-dG]

Maybe there should be a version check if the feature is turned on? If we're less than 1.7, print a warning or something.

[DilumAluthge]

Maybe there should be a version check if the feature is turned on? If we're less than 1.7, print a warning or something.

Good idea! Take a look at the commit I just pushed - does that meet the requirement?

[DilumAluthge]

If it looks good, I'll add it to the other PR as well.

[SaschaMann]

I wonder if instead of adding individual inputs for Pkg.test(;kwargs...) we should take a single input for all kwargs? Or add inputs for every kwarg?

[DilumAluthge]

I wonder if instead of adding individual inputs for Pkg.test(;kwargs...) we should take a single input for all kwargs? Or add inputs for every kwarg?

I don't feel strongly either way. What do you think users would prefer?

[DilumAluthge]

I wonder if instead of adding individual inputs for Pkg.test(;kwargs...) we should take a single input for all kwargs? Or add inputs for every kwarg?

So, we've already added individual inputs for:

• coverage
• depwarn
• inline

So I think probably it would be easiest to just keep the convention of having individual inputs?

[SaschaMann]

Sounds good.

Changes look good to me, I'll merge when the JuliaLang/Pkg.jl#2176 is merged (and leave it on change request until then to prevent accidental merges)

[DilumAluthge]

I've added the "auto-detect Dependabot/CompatHelper" functionality from JuliaLang/Pkg.jl#2234

@christopher-dG @SaschaMann Can you review again?

[SaschaMann]

Should this be considered a breaking change and require a major version bump of the action?

[DilumAluthge]

Hmmm. The only change in behavior is on CompatHelper/Dependabot PRs, right?

Dependabot doesn't exist yet.

And for CompatHelper, this was always supposed to be the intended behavior, so honestly I would consider it to be a bug fix.

[DilumAluthge]

As long as the behavior change is only on Dependabot/CompatHelper PRs, I would say this "technically is a breaking change in behavior, but really it's intended to be a bug fix, so it's okay to do it in a patch release".

[DilumAluthge]

@SaschaMann Take a look now.

[DilumAluthge]

We'll need to wait to merge until the macOS nightlies are fixed.

[DilumAluthge]

Alright the macOS buildbots are fixed and the macOS nightlies are up to date.

This is good to merge from my end.

@SaschaMann

[DilumAluthge]

@SaschaMann Could we make a new v1.x.y tag and release?

[DilumAluthge]

You beat me to it 😂

https://github.com/julia-actions/julia-runtest/releases/tag/v1.6.0

[DilumAluthge]

@SaschaMann and @christopher-dG thank you for your help on this!

[SaschaMann]

I probably should have mentioned that I'm gonna tag it :D

I usually do that right after merging PRs to these actions, I should probably setup a merge-and-tag script at some point.

[DilumAluthge]

🚀 🚀 🚀 it works!!!

https://github.com/cscherrer/SossMLJ.jl/runs/2241088439 (triggered by cscherrer/SossMLJ.jl#132)

┌ Error: Package is not at the latest compatible version
│   name = "CategoricalArrays"
│   uuid = UUID("324d7699-5711-5eae-9e2f-1d82baa6b597")
│   compat_entry_string = "0.8, 0.9"
│   active_version = v"0.8.3"
│   latest_compatible_version = v"0.9.4"
│   earliest_backwards_compatible_version = v"0.9.0"
│   allow_earlier_backwards_compatible_versions = true
└ @ Pkg.Operations /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.7/Pkg/src/Operations.jl:1856
ERROR: One or more direct dependencies is not at the latest compatible version

[DilumAluthge]

I should probably setup a merge-and-tag script at some point.

This could be useful!