Skip to content

Conversation

stanek-michal
Copy link
Contributor

WIP: let's figure out how we want releases to behave.
Perhaps the best way is to manually bump the version and manually make the PR, merge it, push a tag which then triggers Release action? The trigger is:

on:
  push:
    tags:
      - "v*"

Currently release action builds both archs with glibc/musl using docker and prepares the zip with a draft release

@stanek-michal stanek-michal requested a review from a team as a code owner September 12, 2025 15:57
Copy link

cla-checker-service bot commented Sep 12, 2025

💚 CLA has been signed

…musl); strip; tarballs; checksums; CHANGES body
…s, rename to glibc/glibc217, add version check and prepare-release workflow
@@ -0,0 +1,51 @@
name: Prepare Release
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this one maybe can be removed, probably better to do this part manually

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