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

Update sbt-github-actions and sbt-spiewak-sonatype #322

Merged
merged 5 commits into from Jan 2, 2022

Conversation

regadas
Copy link
Collaborator

@regadas regadas commented Dec 2, 2021

No description provided.

build.sbt Outdated Show resolved Hide resolved
@codecov-commenter
Copy link

codecov-commenter commented Dec 2, 2021

Codecov Report

Merging #322 (c44e98e) into main (f309a8b) will decrease coverage by 0.19%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##             main     #322      +/-   ##
==========================================
- Coverage   96.47%   96.28%   -0.20%     
==========================================
  Files           9        9              
  Lines        1049     1049              
  Branches       94       94              
==========================================
- Hits         1012     1010       -2     
- Misses         37       39       +2     
Impacted Files Coverage Δ
core/shared/src/main/scala/cats/parse/Parser.scala 96.06% <0.00%> (-0.24%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f309a8b...c44e98e. Read the comment docs.

Copy link
Collaborator

@johnynek johnynek left a comment

Choose a reason for hiding this comment

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

Wait so this means all users going forward not on 2.11 have to be on Java 11 right?

I'm a bit worried here. What are the pros and cons of adopting Java 11 as the minimum version?

@regadas
Copy link
Collaborator Author

regadas commented Dec 26, 2021

Hi @johnynek!

Wait so this means all users going forward not on 2.11 have to be on Java 11 right?

that's not the intent. We want to target JVM 8 (for now) regardless of the JVM version used to buid/publish the jar. The 2.11 check there exists because that scalac does not support the -release flag only the -target one.

I double checked and class files for the different scala versions have major version: 52

@regadas
Copy link
Collaborator Author

regadas commented Dec 26, 2021

btw, this is required because the underlying plugin that we use for CI switched from 8 to 11 as default and we use it to publish the jars.

@johnynek
Copy link
Collaborator

johnynek commented Jan 2, 2022

sorry for the latency on reviewing this. It looks right to me.

It would be interesting to think about adding some assertion that the built jars have the right class number, but I don't think we should block this (maybe a feature request for sbt-spiewak).

@johnynek johnynek merged commit c8b5519 into typelevel:main Jan 2, 2022
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.

None yet

3 participants