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

replace experimental-binaries with spring-experimental-binaries to avoid version conflict #100

Closed
wants to merge 1 commit into from

Conversation

spoonincode
Copy link
Member

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 in experimental-binaries as if using it as a "bucket", but then the dev packages from a CI run would be stored in separate artifacts such as leap-dev-ubuntu20-amd64 and leap-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

@spoonincode
Copy link
Member Author

oh that's right, v4 doesn't allow this any more. oh well guess will stick with how it is

@spoonincode spoonincode closed this May 1, 2024
@spoonincode spoonincode deleted the spring-experimental-binaries branch May 6, 2024 23:40
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.

experimental-binaries version roll back tag conflict
1 participant