Update inlets-pro version to 0.11.14

[welteki]

Description

Bump the default inlets-pro release used by inletsctl to 0.11.14 for hardened auto-TLS support.

How Has This Been Tested?

Tested against Hetzner with TCP tunnels:

• Deployed current inletsctl default 0.11.13 and verified inlets-pro 0.11.14 client fails without --auto-tls-legacy
• Verified inlets-pro 0.11.14 client connects to the 0.11.13 server with --auto-tls-legacy
• Deployed patched inletsctl default 0.11.14 and verified inlets-pro 0.11.14 client connects without --auto-tls-legacy

How are existing users impacted? What migration steps/scripts do we need?

New servers created by inletsctl will use inlets-pro 0.11.14 by default. Existing servers are not changed and should be recreated or upgraded to get hardened auto-TLS support.

Checklist:

I have:

• updated the documentation and/or roadmap (if required)
• read the CONTRIBUTION guide
• signed-off my commits with git commit -s
• added unit tests

[reviewfn]

AI Pull Request Overview

Disclaimer: This review was generated by automated AI and may contain errors. Do not trust its outputs without human verification.

Summary

• Updates the default inlets-pro version from 0.11.13 to 0.11.14.
• The changed constant is used by inletsctl create as the default --inlets-version value.
• The same constant also feeds generated Kubernetes forwarding manifests through existing package-level usage.
• The user override path for --inlets-version remains unchanged.
• No concrete correctness, migration, or compatibility issue was found in the scoped change.

Approval rating (1-10)

9/10. Low-risk version bump with a narrow diff; remaining risk is limited to release asset availability and runtime compatibility of the external inlets-pro release.

Summary per file

Summary per file

File path	Summary
cmd/create.go	Bumps the default inlets-pro release version to 0.11.14.

Overall Assessment

The scoped change is minimal and aligns with the PR goal of making new inletsctl-provisioned servers use inlets-pro 0.11.14 by default. The override mechanism remains intact, so users can still pin another version when needed. I did not find a specific defect in the changed code.

Detailed Review

Detailed Review

No blocking findings.

The only scoped code change is cmd/create.go, where inletsProDefaultVersion changes from 0.11.13 to 0.11.14. That value is passed into the existing --inlets-version flag default and the fallback for an explicitly empty version, so newly created servers will pick up the intended release without altering the caller override path.

One non-blocking impact to be aware of: inletsProDefaultVersion is package-level and is also used by the Kubernetes forwarding manifest generation in the same package. That means this PR updates more than create provisioning defaults; it also changes the generated ghcr.io/inlets/inlets-pro image tag for those flows. This appears consistent with a global default version bump, but it is worth confirming that this broader default change is intentional.

AI agent details.

Agent processing time: 1m0.917s
Environment preparation time: 3.594s
Total time from webhook: 1m11.766s