-
Notifications
You must be signed in to change notification settings - Fork 92
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
Prepare for v0.8.0 release #380
Conversation
@ssbarnea is it possible to tell Jenkins to release from this branch and only then merge the PR here? |
In theory anything is doable but I do not plan to do the extra work for that, especially as there other shaky thing involved. In fact I am considering delaying this release for next week as is already late friday. |
Co-authored-by: Sviatoslav Sydorenko <[email protected]>
Co-authored-by: Sviatoslav Sydorenko <[email protected]>
Co-authored-by: Sviatoslav Sydorenko <[email protected]>
Fair enough. #no_friday_releases |
I hope we can also fix #373 which is the bug that hindered @priyamsahoo e2e pull-request. We worked around it but the root cause is still very valid. |
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.
Can we also include the recent commit in this release?
Can you please be more explicit? I do not see anything else listed on https://github.com/ansible/vscode-ansible/releases other than the already included 3 items. Also, I am inclined to delay this release until we fix #373 which counts as a serious bug. |
for more information, see https://pre-commit.ci
Co-authored-by: Ansible DevTools <[email protected]>
No description provided.