fix: Set hobby deployments to 'latest' by default #14956
Merged
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.
Problem
This issue was raised in #14865: As we are not publishing any more numbered releases, the
latest-release
Docker tag will get stuck at1.43.0
. Hobby deployments are usinglatest-release
by default, so they will not get the latest features of PostHog by default.Changes
Users should have access to latest PostHog by default, so I've made
latest
the default version for hobby deployments by modifying thedeploy-hobby
script.How did you test this code?
e2e - hobby smoke test
CI should catch any installation errors.