systems/infrastructure
1
Fork 0
Code Issues 1 Pull requests 17 Activity Actions

Update dependency artis3n.tailscale to v4.4.4 #143

Merged
jake merged 1 commit from renovate/artis3n.tailscale-4.x into master 2024-04-15 15:07:16 +01:00
Conversation 0 Commits 1 Files changed 1 +1 -1
renovate commented 2024-03-07 08:00:28 +00:00
Collaborator
Copy link

This PR contains the following updates:

Package Type Update Change
artis3n.tailscale role patch v4.4.2 -> v4.4.4

Release Notes

artis3n/tailscale (artis3n.tailscale)

v4.4.4: 4.4.4

Compare Source

Fixed

  • Debian distros would previously fail to invoke tailscale update due to an incompatible name for the tailscale source list file. This is now corrected. #​449 (Thanks @​cnkk !)

New Contributors

v4.4.3: 4.4.3

Compare Source

Fixed

  • This role will no longer intermittently fail due to colliding variable names with other roles or tasks that may be running in your playbook. This changes internal variable names only, so it is not a breaking change. #​431 (Thanks @​mhitza !)
  • state: absent now fully removes all Tailscale configuration data from your device. Previously, this role would uninstall Tailscale, but that might leave the /var/lib/tailscale directory behind, which contains a tailscaled.state file alongside log files which may contain information about your tailnet. The tailscaled.state file could also hypothetically be used to re-authenticate the server to your tailnet if the server is not de-authorized, however this role runs tailscale logout during uninstallation so the server is always de-authorized from your tailnet. However, I expect users don't want log files, and even stale configuration files, lying around after state: absent. #​435 (Thanks @​McSim85 !) #​444

Changed

  • This repo now uses geerlingguy/docker-debian12-ansible instead of cisagov/docker-debian12-ansible in the CI suite because the cisagov repo has been archived.

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 | patch | `v4.4.2` -> `v4.4.4` | --- ### Release Notes <details> <summary>artis3n/tailscale (artis3n.tailscale)</summary> ### [`v4.4.4`](https://github.com/artis3n/ansible-role-tailscale/releases/tag/v4.4.4): 4.4.4 [Compare Source](https://github.com/artis3n/tailscale/compare/v4.4.3...v4.4.4) #### Fixed - Debian distros would previously fail to invoke `tailscale update` due to an incompatible name for the tailscale source list file. This is now corrected. [#&#8203;449](https://github.com/artis3n/tailscale/issues/449) (Thanks [@&#8203;cnkk](https://github.com/cnkk) !) #### New Contributors - [@&#8203;cnkk](https://github.com/cnkk) made their first contribution in https://github.com/artis3n/ansible-role-tailscale/pull/449 ### [`v4.4.3`](https://github.com/artis3n/ansible-role-tailscale/releases/tag/v4.4.3): 4.4.3 [Compare Source](https://github.com/artis3n/tailscale/compare/v4.4.2...v4.4.3) #### Fixed - This role will no longer intermittently fail due to colliding variable names with other roles or tasks that may be running in your playbook. This changes internal variable names only, so it is not a breaking change. [#&#8203;431](https://github.com/artis3n/tailscale/issues/431) (Thanks [@&#8203;mhitza](https://github.com/mhitza) !) - `state: absent` now fully removes all Tailscale configuration data from your device. Previously, this role would uninstall Tailscale, but that might leave the `/var/lib/tailscale` directory behind, which contains a `tailscaled.state` file alongside log files which may contain information about your tailnet. The `tailscaled.state` file could also hypothetically be used to re-authenticate the server to your tailnet if the server is not de-authorized, however this role runs `tailscale logout` during uninstallation so the server is always de-authorized from your tailnet. However, I expect users don't want log files, and even stale configuration files, lying around after `state: absent`. [#&#8203;435](https://github.com/artis3n/tailscale/issues/435) (Thanks [@&#8203;McSim85](https://github.com/McSim85) !) [#&#8203;444](https://github.com/artis3n/tailscale/issues/444) #### Changed - This repo now uses `geerlingguy/docker-debian12-ansible` instead of `cisagov/docker-debian12-ansible` in the CI suite because the cisagov repo has been archived. #### New Contributors - [@&#8203;mhitza](https://github.com/mhitza) made their first contribution in https://github.com/artis3n/ansible-role-tailscale/pull/431 </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:eyJjcmVhdGVkSW5WZXIiOiIzNy4yMjYuMCIsInVwZGF0ZWRJblZlciI6IjM3LjI1Mi4xIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIn0=-->
renovate changed title from Update dependency artis3n.tailscale to v4.4.3 to Update dependency artis3n.tailscale to v4.4.4 2024-03-18 10:00:37 +00:00
renovate force-pushed renovate/artis3n.tailscale-4.x from 750ce7939c to 5f66a26bfd 2024-03-18 10:00:37 +00:00 Compare
jake merged commit 91ec56717f into master 2024-04-15 15:07:16 +01:00
jake deleted branch renovate/artis3n.tailscale-4.x 2024-04-15 15:07:16 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#143
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?