chore(tailscale-exit-nodes): promote to 1.0.0#81
Merged
Conversation
The control plane has been verified end to end: deploys reach active on both providers, and the reaper tears nodes down at their TTL (including provider firewall cleanup) with no errors. Promote from the 0.x build-out line to 1.0.0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Bumps
images/tailscale-exit-nodesfrom0.1.0to1.0.0.The image was deliberately held on the
0.xbuild-out line until a working end-to-end deployment was confirmed. That bar is now met:activewith a public IP on both providers (AWS Lightsail + Vultr).Removes the now-satisfied "stays on 0.x" comment.
On merge,
container-build-push.ymlrepublishes the image tagged1.0.0/1.0/1.🤖 Generated with Claude Code