Skip to content

feat(ci): Replace S3 upload with a rolling nightly pre-release - #74

Merged
cmainas merged 1 commit into
mainfrom
feat/rolling_release
Sep 16, 2026
Merged

cmainas merged 1 commit into
mainfrom
feat/rolling_release

Conversation

@cmainas

@cmainas cmainas commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Instead of pushing the urunc binaries to the nubificus S3, use a pre-release in GitHUb which will store all the binaries built in the main branch.

Description

Related issues

  • Fixes #

How was this tested?

LLM usage

Checklist

  • I have read the contribution guide.
  • The linter passes locally (make lint).
  • The e2e tests of at least one tool pass locally (make test_ctr, make test_nerdctl, make test_docker, make test_crictl).
  • If LLMs were used: I have read the llm policy.

Instead of pushing the urunc binaries to the nubificus S3, use a
pre-release in GitHUb which will store all the binaries built in the
main branch.

Signed-off-by: Charalampos Mainas <charalampos.mainas@gmail.com>
@cmainas
cmainas force-pushed the feat/rolling_release branch from 5c89a16 to 567f0c4 Compare September 16, 2026 08:08
@cmainas
cmainas merged commit d6b0bc4 into main Sep 16, 2026
6 of 7 checks passed
@cmainas
cmainas deleted the feat/rolling_release branch September 16, 2026 08:10
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.

1 participant