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

Scala 2.13.14, Scala.js 1.16.0 #1078

Merged
merged 1 commit into from
May 2, 2024
Merged

Conversation

SethTisue
Copy link
Contributor

@SethTisue SethTisue commented May 1, 2024

at https://contributors.scala-lang.org/t/scala-2-13-14-release-planning/6581/14 @sjrd said "I might not do earlier [Scala.js] releases" for 2.13.14, so I went ahead and bumped to 1.16.0 — let's see how CI likes it

review by @rochala ?

@SethTisue
Copy link
Contributor Author

Test failure looks like it might be transient, but I don't actually know 🤷

@rochala
Copy link
Collaborator

rochala commented May 2, 2024

The CI is sadly down. Lets merge this as the failure is not connected to your changes.

@rochala rochala merged commit f7cede3 into scalacenter:main May 2, 2024
1 check failed
@rochala
Copy link
Collaborator

rochala commented May 2, 2024

I'll deploy it when everything will be working, as for now there are no mtags for 2.13.14

@SethTisue SethTisue deleted the scala-2.13.14 branch May 2, 2024 13:30
@SethTisue
Copy link
Contributor Author

Hmm. Who publishes mtags? Sounds like the Scala 2 releasing steps should include a "request mtags publishing" step, and perhaps a "wait for mtags to publish" step as well.

@rochala
Copy link
Collaborator

rochala commented May 2, 2024

Ok, so Tomasz is responsible for this, but it seems that the problem is actually in metals version defined in Scastie. I can't deploy it today, will do it tomorrrow with a fix.

@rochala
Copy link
Collaborator

rochala commented May 2, 2024

Ok, nvm I deployed it.

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