Skip to content

fix: use markdown instead of Ansible docs syntax #39

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.

Sign up for GitHub

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

Merged
kangasta merged 2 commits into from
Apr 8, 2026
+1 −1
Merged

fix: use markdown instead of Ansible docs syntax #39

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
73f68c5
fix: use markdown instead of Ansible docs syntax
kangasta Apr 8, 2026
89a2a53
fix: copy fixes from GH release
kangasta Apr 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

### Changed

- Accept list of methods as value to `connect_with`. This allows defining multiple connection methods in order of preference to configure fallback. For example, V(["public_ipv4", "private_ipv4"]) would try to find public IPv4 and fall back to private IPv4 if public IPv4 is not available.
- Accept list of methods as value to `connect_with`. This allows defining multiple connection methods in order of preference to configure fallback. For example, `["public_ipv4", "private_ipv4"]` would try to find public IPv4 and fall back to private IPv4 if public IPv4 is not available.
Comment thread
kangasta marked this conversation as resolved.
Outdated

## [0.9.0] - 2025-11-27

Expand Down
Loading