chore: stop releasing nightlies to central #23797
Merged
+0
−124
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sjrd
approved these changes
Aug 23, 2025
hamzaremmal
added a commit
that referenced
this pull request
Aug 23, 2025
After #23797, there is no path to the `open_issue_on_failure` job. [skip ci]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We currently have a workflow that releases nightlies to https://repo.scala-lang.org.
In this PR, we stop releasing the previous build to Maven Central.
There is a side effect that we stop releasing 3.3.x nightlies here but it'w the other workflow's job to release nightlies to the right repository (PR on its way to release 3.3.x nightlies to https://repo.scala-lang.org too)
[skip ci]