Update dependency artis3n.tailscale to v4.6.0 #221
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "renovate/artis3n.tailscale-4.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v4.5.0
->v4.6.0
Release Notes
artis3n/tailscale (artis3n.tailscale)
v4.6.0
: 4.6.0Compare Source
Ansible tools really want you to be a role inside a collection these days, instead of a standalone role. This role will be migrated to a new collection repo and published onto Galaxy. There should be minor migration work to reference the Collection instead of the Role in your Ansible playbooks, but should not otherwise impact consumers of this role. Mainly, it will wipe my Galaxy download stats which is why I've been putting it off for so long. When the collection is ready, this repo's README will be updated to point to the new collection and then will be archived.
If you would like to provide input into the name of the collection, please join the discussion https://github.com/artis3n/ansible-role-tailscale/discussions/529.
Adds
Removed
Fixed
devcontainer
configuration.tailscale_args_string
iftailscale_tags
is an empty list. https://github.com/artis3n/ansible-role-tailscale/pull/506 (Thanks @UnholyRope !)Changed
stable
vs pinning to 0.22 after a headscale bug required pinning to last known good last year. https://github.com/artis3n/ansible-role-tailscale/pull/527write
scope instead of the deviceswrite
scope.New Contributors
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.