[koterpillar]

This PR adds periodic auto-update of cloudflared to both the CLI and the library.

Both CLI and the library update the downloaded binary every 30 days by default and support:

• Minimum required version for explicit bumps
• Configurable interval
• Option to use an exact version

The interface is backwards compatible.

[changeset-bot]

🦋 Changeset detected

Latest commit: 1b73bd0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
cloudflared	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[JacobLinCool]

Is there a particular reason periodic updates are enabled by default? This changes existing CLI behavior and can cause the same deployment to run a different cloudflared version without any dependency changes. I'd prefer making periodic updates opt-in, while keeping automatic installation for missing binaries and enforcing an explicitly requested minimum version.

[koterpillar]

Perhaps my reasoning comes from a different understanding of what a deployment is. I'm assuming there's a lot of them, they are disposable, and even the same machine might decide to wipe and reinstall the dependency that brings cloudflared in. So I don't want anyone who doesn't periodically reinstall to be at a disadvantage by having an outdated and potentially deprecated version.

I've raised a different PR #43 with no updates by default so you can choose though!