Skip to content
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

Bump julia [compat] to 1.10 (and drop support for 1.6 through 1.9) #1005

Merged
merged 4 commits into from
Nov 25, 2024

Conversation

KristofferC
Copy link
Member

The CI matrix has ballooned up to a ridiculous number of combinations at this point. First step to reduce it seems to be to stop supporting and testing unsupported julia releases.

@DilumAluthge
Copy link
Member

Dropping some old CI jobs seems okay. Is it necessary to bump the Julia compat? We could just leave the Julia compat as is, and if new PackageCompiler releases continue to work on old Julia releases, that seems fine, right?

I think it'd be nice to at least keep compatibility with 1.6 for now, since it was the LTS for a long time, and there are likely still people using it.

test/runtests.jl Outdated
@@ -117,7 +105,7 @@ end
@info "starting: create_app testset" incremental filter
tmp_app_source_dir = joinpath(tmp, "MyApp")
cp(app_source_dir, tmp_app_source_dir)
if is_gha_ci && (is_julia_1_6 || is_julia_1_9)
if is_gha_ci
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You'd want to remove this entire if-end block.

@KristofferC
Copy link
Member Author

People can still use PackageCompiler with 1.6.

I think getting rid of a bunch of old version checks to simplify the code is worth it. For example I think

function create_sysimage_workaround(
could be removed now as well.

Copy link

codecov bot commented Nov 22, 2024

Codecov Report

Attention: Patch coverage is 75.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 86.19%. Comparing base (530b392) to head (2d1b072).
Report is 1 commits behind head on master.

Files with missing lines Patch % Lines
src/PackageCompiler.jl 75.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1005      +/-   ##
==========================================
- Coverage   87.73%   86.19%   -1.54%     
==========================================
  Files           3        3              
  Lines         799      797       -2     
==========================================
- Hits          701      687      -14     
- Misses         98      110      +12     

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


🚨 Try these New Features:

@DilumAluthge DilumAluthge changed the title bump julia compat to 1.10 Bump julia compat to 1.10 (and drop support for 1.6 through 1.9) Nov 23, 2024
@DilumAluthge DilumAluthge changed the title Bump julia compat to 1.10 (and drop support for 1.6 through 1.9) Bump julia compat to 1.10 (and drop support for 1.6 through 1.9) Nov 23, 2024
Copy link
Member

@DilumAluthge DilumAluthge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally, I don't think that the relatively minor (IMO) code simplifications are worth dropping support for 1.6. My thinking is that 1.6 was the LTS for a long time, so people are probably going to keep using 1.6 for a while, and it would be nice for those users to keep getting PackageCompiler improvements.

That all being said, I don't feel particularly strongly about this, so I won't stand in the way.

We should make the next PackageCompiler release 2.2.0. That way, if we do end up needing to backport a bug fix, we can do so in the 2.1.x release series.

@DilumAluthge DilumAluthge changed the title Bump julia compat to 1.10 (and drop support for 1.6 through 1.9) Bump julia [compat] to 1.10 (and drop support for 1.6 through 1.9) Nov 25, 2024
@KristofferC KristofferC merged commit 6777978 into master Nov 25, 2024
18 of 20 checks passed
@KristofferC KristofferC deleted the kc/1.10 branch November 25, 2024 10:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants