Linux package repository migration + automatic release #8
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.
PR implementing ongoing effort of migration from JFrog and securing sbt repository: https://contributors.scala-lang.org/t/roadmap-for-the-sbt-community-repository/6195
This PR focuses on 2 aspects:
sbt/sbt
repository). This is important to have proper automation, as it won't require any input from the maintainers to have it released (right now version 1.9.3 of sbtn is not published nor released)On top of that, this should answer a few reported issues such as:
apt install sbt
but required an additional flag selecting the amd64 architecture, despite the fact sbtn is platform independent.This will require changes in
sbt/sbt
such as adding additional CI which will run the deployment in this repository and also update sbtn-version to the released onehttps://github.com/sbt/sbt/blob/1.9.x/sbt#L27 with possible fallback. This PR may require additional changes to separate building and signing linux packages from native client building.
All the packages in this PR are signed with different key, as secrets are not yet setup in this repository.