README.md,action.yml: bump versions #42
Merged
Conversation
This file contains 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
Signed-off-by: Irbe Krumina <irbe@tailscale.com>
irbekrm
commented
Jun 14, 2024
| @@ -49,4 +49,4 @@ runs: | |||
| TS_OAUTH_SECRET: "${{ inputs.oauth-secret }}" | |||
| TS_API_KEY: "${{ inputs.api-key }}" | |||
| TS_TAILNET: "${{ inputs.tailnet }}" | |||
| run: go run tailscale.com/cmd/gitops-pusher@v1.62.0 "--policy-file=${{ inputs.policy-file }}" "${{ inputs.action }}" | |||
| run: go run tailscale.com/cmd/gitops-pusher@v1.66.4 "--policy-file=${{ inputs.policy-file }}" "${{ inputs.action }}" | |||
There was a problem hiding this comment.
There haven't been any changes to gitops pusher since 1.62 https://github.com/tailscale/tailscale/tree/main/cmd/gitops-pusher
willnorris
approved these changes
Jun 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This version bump is pretty much a no-op, I just wanted to bump things before cutting a new tag.
I have tested (using my fork of this repo) that an action with changes from this PR succeeds. (Additionally, I have tested that the cache errors that were reported in #41 and #36 are not present in build from main).
Once this PR merges, I will cut a new tag and create a new Github release