Skip to content

Intro Release Setup#113

Merged
juliangieseke merged 3 commits intoalphafrom
jg/release-setup
Nov 10, 2025
Merged

Intro Release Setup#113
juliangieseke merged 3 commits intoalphafrom
jg/release-setup

Conversation

@juliangieseke
Copy link
Contributor

@juliangieseke juliangieseke commented Nov 5, 2025

Introducing a release process for hypha binaries and its driver. Also sets all versions in the repo to 0.0.0.

As for the release workflow, I extracted some bits from the old validate workflow and did some renaming here and there, happy to discuss/change details.

Currently released artifacts are as follows:
Screenshot 2025-11-07 at 13 48 49

I decided to stop here for now, as binaries can be downloaded from our public releases and for the drivers, pip is able to also install directly from a Github release via pip install https://github.com/OWNER/REPO/releases/download/v1.0.0/yourpkg-1.0.0-py3-none-any.whl

Closes #83

@juliangieseke juliangieseke force-pushed the jg/release-setup branch 7 times, most recently from 7a4e9d9 to 1817972 Compare November 5, 2025 09:52
@codecov
Copy link

codecov bot commented Nov 5, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@juliangieseke juliangieseke force-pushed the jg/release-setup branch 13 times, most recently from 395bf1d to 6065207 Compare November 6, 2025 10:40
@juliangieseke juliangieseke changed the base branch from main to alpha November 6, 2025 14:41
@juliangieseke juliangieseke changed the title Release Setup Intro Release Setup Nov 7, 2025
@juliangieseke juliangieseke marked this pull request as ready for review November 7, 2025 12:57
@juliangieseke
Copy link
Contributor Author

Last run from this branch for reference: https://github.com/hypha-space/hypha/actions/runs/19168917959

@juliangieseke
Copy link
Contributor Author

Also once this is merged we need to check the required checks.. I think this just being a PR messes a couple things up in the settings pane 🙈

Copy link
Contributor

@nfnt nfnt left a comment

Choose a reason for hiding this comment

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

This looks good to me once we remove the Python build step, as we currently don't work with modules. I will however check, if we can change how we call accelerate with the Python code... it may be possible to call a module here (accelerate launch -m) instead of a script, which would make it easier for us to distribute the Python part.

@juliangieseke
Copy link
Contributor Author

juliangieseke commented Nov 10, 2025

only saving cache from release branch workflow LGTM:

@juliangieseke juliangieseke force-pushed the jg/release-setup branch 2 times, most recently from 8251e60 to da8145a Compare November 10, 2025 16:32
@juliangieseke
Copy link
Contributor Author

Ok, all updates done. PTAL and then I need to figure our how these requirement rules work 🙈

Introduce a simple release process that creates github releases and adds all necessary artifacts
@juliangieseke
Copy link
Contributor Author

Ok, I think I figured out the required checks. PR should be ready to merge now (pending review)

@juliangieseke juliangieseke merged commit 14a80d2 into alpha Nov 10, 2025
9 checks passed
@juliangieseke juliangieseke deleted the jg/release-setup branch November 10, 2025 20:32
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.

CI: Introduce A Release Workflow

3 participants