replace experimental-binaries
with spring-experimental-binaries
to avoid version conflict
#100
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.
Change the package name that dev.deb packages are stored in to avoid a version conflict in a few releases, fixes #50
Since we have to touch all downstream users of
leap-dev.deb
->spring-dev.deb
anyways, this also makes another modification to eliminate a long standing inconsistency. Previously, all dev packages corresponding to a release were stored inexperimental-binaries
as if using it as a "bucket", but then the dev packages from a CI run would be stored in separate artifacts such asleap-dev-ubuntu20-amd64
andleap-dev-ubuntu22-amd64
. But the thing is, an artifact is actually a bucket too. So for consistency just use a single artifact:spring-dev-deb-amd64
.asset-artifact-download-action
seems prepared to handle multiple files in an artifact,https://github.com/AntelopeIO/asset-artifact-download-action/blob/87f9193fddc71d0515ee1d3cac929e0b4d6bd503/main.mjs#L79-L88