-
Notifications
You must be signed in to change notification settings - Fork 563
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
Improve releasing during v0.11.3 #7319
Conversation
Due to #7320, we can't merge this as is - we need to either: run the next release with 0.11.2 (instead of 0.11.3), or modify our I think it's probably worth adapting to the regression and temporarily disabling the list of scalars for the time being. |
Yup! I guess we just have to wait to see if it happens 👀
Just pushed a commit for it, we can revert it once v0.11.4 releases.
Excellently 🎉 I literally just copy-pasted them, works perfectly ❤️ |
Before we merge this, I would like to add some more details for the dagger-for-github release so that we have a quick fix for what @jpadams was mentioning earlier today. Taking that action item on as I review & merge this. |
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.
This now looks good to me!
OK to merge when all checks pass 👍 🚀
Signed-off-by: Justin Chadwell <me@jedevc.com>
Signed-off-by: Justin Chadwell <me@jedevc.com>
Signed-off-by: Justin Chadwell <me@jedevc.com>
Signed-off-by: Justin Chadwell <me@jedevc.com>
Signed-off-by: Justin Chadwell <me@jedevc.com>
Signed-off-by: Justin Chadwell <me@jedevc.com>
Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
9ca7294
to
4cd1863
Compare
Signed-off-by: Justin Chadwell me@jedevc.com