Deprecate py3.8 and deal with action warnings

[unkcpz]

No description provided.

[codecov]

Codecov Report

Patch coverage has no change and project coverage change: +0.22 🎉

Comparison is base (d3c121f) 86.54% compared to head (466cba0) 86.76%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #183      +/-   ##
==========================================
+ Coverage   86.54%   86.76%   +0.22%     
==========================================
  Files           9        9              
  Lines         907      907              
==========================================
+ Hits          785      787       +2     
+ Misses        122      120       -2     

Flag	Coverage Δ
py-3.10	86.65% <ø> (+0.22%)	⬆️
py-3.11	86.43% <ø> (ø)
py-3.8	?
py-3.9	86.50% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[danielhollas]

Why deprecate 3.8? That is still a version in use by older Linux distros I think, let's not make things more complicated for potential users.

[unkcpz]

Okay, that is true, I was at this repo on other changes and find this from README https://github.com/aiidalab/aiidalab-launch#compatibility.

[danielhollas]

Interesting. TBH I don't really see a reason why this package should follow NEP 29. This package does not depend on the Python scientific ecosystem (numpy et al). On the contrary, since it is a CLI tool, it's likely to be installed system-wide using Linux distribution Python, that is often lagging behind. So I would simply vote for not following NEP 29.

[unkcpz]

Yes, agree. I close this PR.