-
Notifications
You must be signed in to change notification settings - Fork 37
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
Testing for v0.21.0 Release candidate & Final #42
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that a final v0.21.0 has been tagged, it'd be great to have a release soon. Is there still an issue with this code or has it just not been tested enough yet?
I've been running the release candidates fine on one of my nodes for a whole month (other than the V3 issue, its all good) Thanks for the review @AaronDewes |
I've switched it back to the official release and will merge if everything looks good |
tagged and being built as we speak |
Built - in testing now Just some issues with the release scripts right now (DNS it seems) |
I've also sent a Pull Request to umbrel |
Documentation pertaining to Merging this in, and will address any other issues with blocking failed building (so far there is an issue uploading release assets due to some DNS error, which has nothing to do with the docker releases. I would also like to add in another alternate docker hub too (GHCR and maybe gitlab too) in future so we are more resilient to decentralization |
Testing for v0.21.0 Release candidate