Skip to content
This repository was archived by the owner on May 6, 2025. It is now read-only.

fix(gha): add release-please #481

Merged
merged 1 commit into from
Feb 3, 2024
Merged

fix(gha): add release-please #481

merged 1 commit into from
Feb 3, 2024

Conversation

ruzickap
Copy link
Owner

@ruzickap ruzickap commented Jul 4, 2023 •
edited
Loading

Fix Vagrant issue:

An error occurred executing a remote WinRM command.

Shell: Cmd
Command: hostname
Message: Digest initialization failed: initialization error
Error: Process completed with exit code 1.

@ruzickap ruzickap force-pushed the fix-vagrant branch 2 times, most recently from df072be to c57161b Compare July 5, 2023 04:32
@github-actions
Copy link
Contributor

github-actions bot commented Aug 5, 2023

This pull request has been automatically marked as stale because it
has not had recent activity. It will be closed if no further activity
occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale label Aug 5, 2023
@ruzickap ruzickap removed the Stale label Aug 5, 2023
@abbbi
Copy link
Contributor

abbbi commented Aug 10, 2023

hi,

thats an issue in vagrant fixed in the latest vagrant 2.3.8 dev build

@ruzickap
Copy link
Owner Author

Good to know - then I need to wait for 2.3.8 release :-)
Thank you for letting me know...

@abbbi
Copy link
Contributor

abbbi commented Aug 10, 2023

heres the reference: hashicorp/vagrant#13211 (comment)

@github-actions
Copy link
Contributor

This pull request has been automatically marked as stale because it
has not had recent activity. It will be closed if no further activity
occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale label Sep 10, 2023
@ruzickap ruzickap removed the Stale label Sep 11, 2023
@ricopicone
Copy link

heres the reference: hashicorp/vagrant#13211 (comment)

I'm getting this error on a macOS (arm) host with the latest nightly build. The link provided doesn't have a darwin build. Is there a fixed version for my situation? Thanks!

@ruzickap
Copy link
Owner Author

ruzickap commented Oct 8, 2023

Currently the builds are broken.
I hope Vagrant v2.3.8 will solve this situation. Once there will be a new "stable" version I will look at it...

If there are bugs in the "nightly" feel free to report it to Vagrant - I probably can not help with it :-(

Thanks...

@braaqwesi
Copy link

Does this fix works for MaC OSx.. i am stil facing the issue

@ruzickap
Copy link
Owner Author

I doubt...
Maybe new Vagrant release v2.3.8 will help...

@github-actions GitHub Actions
Copy link
Contributor

This pull request has been automatically marked as stale because it
has not had recent activity. It will be closed if no further activity
occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale label Nov 14, 2023
@github-actions github-actions bot removed the Stale label Nov 15, 2023
@ruzickap ruzickap force-pushed the fix-vagrant branch 3 times, most recently from 6e0cf73 to c48f8fc Compare November 17, 2023 19:00
@pull-request-size pull-request-size bot added size/M and removed size/S labels Nov 17, 2023
@ruzickap ruzickap force-pushed the fix-vagrant branch 3 times, most recently from 1ca628b to 8f407c3 Compare November 18, 2023 09:49
@ruzickap ruzickap force-pushed the fix-vagrant branch 7 times, most recently from 3c6789d to 9aff52c Compare November 19, 2023 18:20
@github-actions GitHub Actions
Copy link
Contributor

This pull request has been automatically marked as stale because it
has not had recent activity. It will be closed if no further activity
occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale label Dec 20, 2023
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Jan 3, 2024

This pull request has not seen any activity since it was marked stale.
Closing.

@github-actions github-actions bot closed this Jan 3, 2024
@ruzickap ruzickap reopened this Jan 3, 2024
@ruzickap ruzickap removed the Stale label Jan 3, 2024
@ruzickap ruzickap force-pushed the fix-vagrant branch 2 times, most recently from 031955f to 8724a2a Compare January 31, 2024 16:34
@ruzickap ruzickap changed the title fix(build): fix vagrant issue related to WinRM fix(build): add release-please Feb 3, 2024
@ruzickap ruzickap changed the title fix(build): add release-please fix(gha): add release-please Feb 3, 2024
@ruzickap ruzickap force-pushed the fix-vagrant branch 2 times, most recently from e76cbf0 to 9538bf5 Compare February 3, 2024 19:56
@ruzickap ruzickap merged commit 5a1ab3d into main Feb 3, 2024
@ruzickap ruzickap deleted the fix-vagrant branch February 3, 2024 20:00
@github-actions github-actions bot mentioned this pull request Feb 3, 2024
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
size/M
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@ruzickap @abbbi @ricopicone @braaqwesi