Pass depwarn in via julia_args

[SamuelBrand1]

This PR aims to fix #49 by passing the depwarn choice to julia_args when test is called. At the moment (I think), the julia process Pkg.test is called from has a flexible depwarn but the actual test process generated by that falls back to default. So the only catch on depreciation warnings is if the outer process has --depwarn=error.

PS I've follow the same pattern as other env vars being passed to julia_args argument of test.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (8ce963b) to head (4512dd4).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #135   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines            2         2           
=========================================
  Hits             2         2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[SamuelBrand1]

Thats interesting because I'm seeing the same thing as the issue... i.e. dep warnings still seem to be happening. Could this be a force option from the code maintainers?

[omus]

Do you have a reference to a workflow that is getting unexpected deprecation warnings/errors?

[SamuelBrand1]

Hey @omus .

Here is one https://github.com/CDCgov/Rt-without-renewal/actions/runs/12877933673/job/35903139971?pr=581

Going into the julia-runtest step you can see that the julia_cmd is julia --color=yes --depwarn=no --inline=yes --project=@. -e 'include(joinpath(ENV["GITHUB_ACTION_PATH"], "test_harness.jl"))' but plenty of depreciation warnings further down.

I'm trying to move to a situation where the main testing does not do depwarn because this seems to cause significant slow down, whilst having one CI aimed at capturing dep warnings.

[omus]

Thanks. I tracked the issue down to this line in Pkg.jl. According to the PR which introduced that line we need to rely on overriding that flag via julia_actions like you propose.

If you remove the --depwarn flag from action.yaml I'm good to move ahead with this.

[SamuelBrand1]

@omus thanks for looking at this.

[omus]

LGTM. I suggested a comment for code maintainers