systems/infrastructure
1
Fork 0
Code Issues1 Pull requests20 Activity Actions

Update dependency artis3n.tailscale to v5 #229

Open
renovate wants to merge 1 commit from renovate/artis3n.tailscale-5.x into master
Conversation 0 Commits 1 Files changed 1 +1 -1
renovate commented 2025-03-08 18:00:33 +00:00
Collaborator

This PR contains the following updates:

Package Type Update Change
artis3n.tailscale role major v4.5.0 -> v5.0.1

Release Notes

artis3n/tailscale (artis3n.tailscale)

v5.0.1: 5.0.1

Compare Source

Fixed

  • CentOS reinstallations would previously fail - install, uninstall, then install again. This was due to improper cleanup of the tailscale dnf repos in state: absent scenarios on CentOS distributions. This is now fixed. #​538 (Thanks @​dbrennand !)

New Contributors

v5.0.0: 5.0.0

Compare Source

[!IMPORTANT]
This standalone role is now part of a new collection, https://github.com/artis3n/ansible-collection-tailscale

Should be a drop-in replacement to this role. Take a look and provide feedback in that new repo.

Breaking Changes

  • This role now uses the end_role option of ansible.builtin.meta, which was first introduced in ansible-core 2.18. Therefore, the minimum required version of ansible-core has been bumped to 2.18. This version of ansible-core is only bundled into ansible 11.x.

Added

  • Added a migration warning notice about the new collection repository.

Changed

  • Deprecated legacy, EOL distros in the CI suite due to new minimum Python version requirements in Ansible 11.x.

v4.6.0: 4.6.0

Compare Source

[!IMPORTANT]
This will be one of the last releases on this Ansible role before it is migrated into a Collection.

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

  • Removed CentOS 7 as a supported distro in July 2024 due to being EOL. While Tailscale can still be installed on CentOS 7, modern Ansible's minimum requirements exceed a default CentOS 7 installation.

Fixed

Changed

  • Updated Python dependencies
  • Updated CI dependencies
  • Migrated headscale in CI to 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/527
  • Updated the README to indicate that OAuth keys now only need the auth keys write scope instead of the devices write 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.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [artis3n.tailscale](https://github.com/artis3n/tailscale) | role | major | `v4.5.0` -> `v5.0.1` | --- ### Release Notes <details> <summary>artis3n/tailscale (artis3n.tailscale)</summary> ### [`v5.0.1`](https://github.com/artis3n/ansible-role-tailscale/releases/tag/v5.0.1): 5.0.1 [Compare Source](https://github.com/artis3n/tailscale/compare/v5.0.0...v5.0.1) #### Fixed - CentOS reinstallations would previously fail - install, uninstall, then install again. This was due to improper cleanup of the tailscale `dnf` repos in `state: absent` scenarios on CentOS distributions. This is now fixed. [#&#8203;538](https://github.com/artis3n/tailscale/issues/538) (Thanks [@&#8203;dbrennand](https://github.com/dbrennand) !) #### New Contributors - [@&#8203;dbrennand](https://github.com/dbrennand) made their first contribution in https://github.com/artis3n/ansible-role-tailscale/pull/538 ### [`v5.0.0`](https://github.com/artis3n/ansible-role-tailscale/releases/tag/v5.0.0): 5.0.0 [Compare Source](https://github.com/artis3n/tailscale/compare/v4.6.0...v5.0.0) > \[!IMPORTANT] > This standalone role is now part of a new collection, https://github.com/artis3n/ansible-collection-tailscale > > Should be a drop-in replacement to this role. Take a look and provide feedback in that new repo. #### Breaking Changes - This role now uses the `end_role` option of `ansible.builtin.meta`, which was first introduced in `ansible-core` 2.18. Therefore, the minimum required version of ansible-core has been bumped to 2.18. This version of `ansible-core` is only bundled into `ansible` 11.x. #### Added - Added a migration warning notice about the new collection repository. #### Changed - Deprecated legacy, EOL distros in the CI suite due to new minimum Python version requirements in Ansible 11.x. ### [`v4.6.0`](https://github.com/artis3n/ansible-role-tailscale/releases/tag/v4.6.0): 4.6.0 [Compare Source](https://github.com/artis3n/tailscale/compare/v4.5.0...v4.6.0) > \[!IMPORTANT] > **This will be one of the last releases on this Ansible role before it is migrated into a Collection.** 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 - Added Ubuntu 24.04 as a supported distro in July 2024. - Added support for Linux Mint. https://github.com/artis3n/ansible-role-tailscale/pull/515 (Thanks [@&#8203;fkonradmain](https://github.com/fkonradmain) !) #### Removed - Removed CentOS 7 as a supported distro in July 2024 due to being EOL. While Tailscale can still be installed on CentOS 7, modern Ansible's minimum requirements exceed a default CentOS 7 installation. #### Fixed - Fixed broken `devcontainer` configuration. - Fixed templating of `tailscale_args_string` if `tailscale_tags` is an empty list. https://github.com/artis3n/ansible-role-tailscale/pull/506 (Thanks [@&#8203;UnholyRope](https://github.com/UnholyRope) !) #### Changed - Updated Python dependencies - Updated CI dependencies - Migrated headscale in CI to `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/527 - Updated the README to indicate that OAuth keys now only need the auth keys `write` scope instead of the devices `write` scope. #### New Contributors - [@&#8203;UnholyRope](https://github.com/UnholyRope) made their first contribution in https://github.com/artis3n/ansible-role-tailscale/pull/506 - [@&#8203;fkonradmain](https://github.com/fkonradmain) made their first contribution in https://github.com/artis3n/ansible-role-tailscale/pull/515 </details> --- ### 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40NDAuNyIsInVwZGF0ZWRJblZlciI6IjM3LjQ0MC43IiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbXX0=-->
renovate added 1 commit 2025-03-08 18:00:33 +00:00
renovate force-pushed renovate/artis3n.tailscale-5.x from faebc88d26 to 4a409b26dd 2025-04-03 08:00:43 +01:00 Compare
All checks were successful
/ terraform (push) Successful in 1m24s
Details
/ ansible (push) Successful in 2m37s
Details
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/artis3n.tailscale-5.x:renovate/artis3n.tailscale-5.x
git checkout renovate/artis3n.tailscale-5.x

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.

git checkout master
git merge --no-ff renovate/artis3n.tailscale-5.x
git checkout renovate/artis3n.tailscale-5.x
git rebase master
git checkout master
git merge --ff-only renovate/artis3n.tailscale-5.x
git checkout renovate/artis3n.tailscale-5.x
git rebase master
git checkout master
git merge --no-ff renovate/artis3n.tailscale-5.x
git checkout master
git merge --squash renovate/artis3n.tailscale-5.x
git checkout master
git merge --ff-only renovate/artis3n.tailscale-5.x
git checkout master
git merge renovate/artis3n.tailscale-5.x
git push origin master
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: systems/infrastructure#229
No description provided.
Delete branch "renovate/artis3n.tailscale-5.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?