Tentacle versioning and when to update

Octopus Deploy employs GitVersion to manage the semantic versioning of its builds, allowing for efficient version control across projects in a single repository, though this results in synchronized versioning regardless of individual project changes. The Octopus Server often gets updated alongside the Tentacle installer, but users are reassured that upgrading the Tentacle isn't necessary with each server update, as Tentacle updates are less frequent and its code changes infrequently. Tentacle 3.1 and above require .NET 4.5 to support TLS 1.2, limiting upgrades on older Windows servers, but Octopus provides a lock feature to maintain current Tentacle versions without updates and allows users to dismiss update notifications for Tentacle when they are unnecessary. The organization plans to separate the Tentacle project into its own repository to avoid versioning confusion, and while changes to the Tentacle versioning process are expected in the future, users can currently disregard Tentacle version updates unless significant changes are noted in the release notes.