Skip to content

chore(code): batch releases on 16h cadence#1938

Merged
jonathanlab merged 3 commits intomainfrom
posthog-code/batched-releases
Apr 29, 2026
Merged

chore(code): batch releases on 16h cadence#1938
jonathanlab merged 3 commits intomainfrom
posthog-code/batched-releases

Conversation

@jonathanlab
Copy link
Copy Markdown
Contributor

@jonathanlab jonathanlab commented Apr 29, 2026

Update our release schedule to release every 16 hours:

  • Once at 17:00 UTC / 18:00 CET / 09:00 PT
  • Once at 01:00 UTC / 02:00 CET / 17:00 PT

I chose these timeframes so all your work is batched and released at the end of your workday (17:00 UTC or 17:00 PT)

updated readme
Also add a label Create release which can be used for hotfixes

Tag workflow now runs at 17:00 and 01:00 UTC instead of every push to main.
Merging a PR labeled "create release" still ships immediately.

Generated-By: PostHog Code
Task-Id: 19a0f519-b88d-4985-926f-c437ff3328ff
@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Apr 29, 2026

Prompt To Fix All With AI
This is a comment left during a code review.
Path: apps/code/README.md
Line: 131

Comment:
**Scheduled times don't match the cron**

The bullet says "automatic at **00:00 and 12:00 UTC**", but the cron `"0 1,17 * * *"` fires at **01:00 and 17:00 UTC** — matching the correct times stated in the prose paragraph just above. The bullet needs to be updated to avoid confusion.

```suggestion
1. **Scheduled (default)** — automatic at 01:00 and 17:00 UTC.
```

How can I resolve this? If you propose a fix, please make it concise.

Reviews (1): Last reviewed commit: "chore(code): batch releases on 12h caden..." | Re-trigger Greptile

Comment thread apps/code/README.md Outdated
@jonathanlab jonathanlab marked this pull request as draft April 29, 2026 10:49
Generated-By: PostHog Code
Task-Id: 19a0f519-b88d-4985-926f-c437ff3328ff
@jonathanlab jonathanlab marked this pull request as ready for review April 29, 2026 10:52
Generated-By: PostHog Code
Task-Id: 19a0f519-b88d-4985-926f-c437ff3328ff
@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Apr 29, 2026

Prompt To Fix All With AI
This is a comment left during a code review.
Path: .github/workflows/code-tag.yml
Line: 5

Comment:
**Cron intervals are 8h and 16h, not 12h**

`"0 1,17 * * *"` fires at 01:00 and 17:00 UTC — 16 hours apart in one direction and 8 hours in the other. For a true 12h cadence (as the PR title and README "12h" phrasing implies), the two fire times need to be exactly 12 hours apart, e.g. `"0 1,13 * * *"` or `"0 5,17 * * *"`.

How can I resolve this? If you propose a fix, please make it concise.

Reviews (2): Last reviewed commit: "chore(code): capitalize release label na..." | Re-trigger Greptile

@jonathanlab jonathanlab changed the title chore(code): batch releases on 12h cadence chore(code): batch releases on 16h cadence Apr 29, 2026
@jonathanlab jonathanlab merged commit c523435 into main Apr 29, 2026
15 checks passed
@jonathanlab jonathanlab deleted the posthog-code/batched-releases branch April 29, 2026 11:03
charlesvien added a commit that referenced this pull request May 4, 2026
## Problem

The 24h update check interval causes users to download a stale update, restart and immediately see another update waiting. The client already re-checks even when an update is staged (periodic checks bypass the updateReady guard), but the 24h window is too long to catch newer versions before the user clicks restart.

**NOTE:** Since #1938, releases are batched on a 16h cadence instead of shipping on every merge, so it should no longer be the responsibility of the clients to scatter updates and we should actually want to pull the latest updates as soon as possible now because if we push a hotfix we want users to get it sooner than later and we are no longer spammy with our normal commit updates.

<!-- Who is this for and what problem does it solve? -->

<!-- Closes #ISSUE_ID -->

## Changes

1. Reduce CHECK_INTERVAL_MS from 24 hours to 1 hour
2. Update test to match new interval

<!-- What did you change and why? -->

<!-- If there are frontend changes, include screenshots. -->

## How did you test this?

Manually
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants