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

[ci] Bump to JDK 21 #4632

Merged
merged 1 commit into from
Jan 20, 2025
Merged

[ci] Bump to JDK 21 #4632

merged 1 commit into from
Jan 20, 2025

Conversation

unlsycn
Copy link
Contributor

@unlsycn unlsycn commented Jan 20, 2025

This is an addition to #4616 and should fix #4616 (comment) as Mill has dropped support for Java 8 since 0.12(Changelog).

cc @seldridge @jackkoenig

Contributor Checklist

  • Did you add Scaladoc to every public function/method?
  • Did you add at least one test demonstrating the PR?
  • Did you delete any extraneous printlns/debugging code?
  • Did you specify the type of improvement?
  • Did you add appropriate documentation in docs/src?
  • Did you request a desired merge strategy?
  • Did you add text to be included in the Release Notes for this change?

Type of Improvement

  • Feature (or new API)
  • API modification
  • API deprecation
  • Backend code generation
  • Performance improvement
  • Bugfix
  • Documentation or website-related
  • Dependency update
  • Internal or build-related (includes code refactoring/cleanup)

Desired Merge Strategy

  • Squash: The PR will be squashed and merged (choose this if you have no preference).
  • Rebase: You will rebase the PR onto master and it will be merged with a merge commit.

Release Notes

Reviewer Checklist (only modified by reviewer)

  • Did you add the appropriate labels? (Select the most appropriate one based on the "Type of Improvement")
  • Did you mark the proper milestone (Bug fix: 3.6.x, 5.x, or 6.x depending on impact, API modification or big change: 7.0)?
  • Did you review?
  • Did you check whether all relevant Contributor checkboxes have been checked?
  • Did you do one of the following when ready to merge:
    • Squash: You/ the contributor Enable auto-merge (squash), clean up the commit message, and label with Please Merge.
    • Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

Signed-off-by: unlsycn <unlsycn@unlsycn.com>
@sequencer sequencer added the Dependency Update Updates a dependency, will be included in release notes label Jan 20, 2025
@sequencer
Copy link
Member

I think this pump is OK. If there are something concerned, for example the jvm version is too new, we can downgrade it to 17.

@sequencer sequencer added Please Merge Accepted PRs that are ready to be merged. Useful when waiting on CI. Panama Related to Panama Binding Framework labels Jan 20, 2025
Comment on lines -52 to -55
// Older versions of Scala do not work with newer versions of the JVM
// This is a hack to ensure we always use Java 8 to publish Chisel with Scala 2.13
// We could use Java 11 with -release 8
// Note that this target is used by real publishing but not by publishLocal
Copy link
Member

Choose a reason for hiding this comment

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

I think we don't need to support older version of Scala, bumping Scala version is always safe. Feel free to revert it.

@chiselbot chiselbot merged commit ac250b1 into chipsalliance:main Jan 20, 2025
21 of 22 checks passed
@sequencer
Copy link
Member

Let's see if the release flow is passed. If not, @unlsycn please remove the older version of Scala.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dependency Update Updates a dependency, will be included in release notes Panama Related to Panama Binding Framework Please Merge Accepted PRs that are ready to be merged. Useful when waiting on CI.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants