We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Latest
What do you think of having a Latest release on GitHub which is constantly updated whenever we merge something into main? We could use this to attach
main
coordinator
maker
webapp
Originally posted by @bonomat in #1943 (comment)
The text was updated successfully, but these errors were encountered:
You mean whenever we release right? In the context of apk releases, we still have to make sure that the coordinator is upgraded in coordination.
If not what benefits do you see in releasing every merge to main?
Sorry, something went wrong.
You mean whenever we release right?
No, I mean whenever we merge, like a nightly release, just not nightly, but whenever we merge.
The benefits are:
It might be confusing though if this is called latest because people might understand that this is the latest stable release.
In the context of apk releases, we still have to make sure that the coordinator is upgraded in coordination.
The default values will go against our regtest setup.
No branches or pull requests
What do you think of having a
Latest
release on GitHub which is constantly updated whenever we merge something intomain
? We could use this to attachcoordinator
/maker
,webapp
Originally posted by @bonomat in #1943 (comment)
The text was updated successfully, but these errors were encountered: