Skip to content

chore: cleanup prompts#3804

Open
rebelchris wants to merge 4 commits intomainfrom
chore-cleanup-prompts
Open

chore: cleanup prompts#3804
rebelchris wants to merge 4 commits intomainfrom
chore-cleanup-prompts

Conversation

@rebelchris
Copy link
Copy Markdown
Contributor

Cleanup prompts

@pulumi
Copy link
Copy Markdown

pulumi Bot commented Apr 16, 2026

🍹 The Update (preview) for dailydotdev/api/prod (at 4a8285e) was successful.

✨ Neo Explanation

Routine deployment promoting commit `544f4b1c` to all deployments and cron jobs, with DB and Clickhouse migration jobs executing as part of the release — confirm migrations are backward-compatible with the live application. ✅ Low Risk

This is a standard application deployment rolling out commit 544f4b1c (replacing 0b7efa68) across all services. Every change is a container image tag bump and version label update — no configuration, resource sizing, or structural changes are involved.

The two migration Jobs (DB and Clickhouse) follow the expected pattern: old Jobs tied to the previous commit hash are deleted and new ones for the new commit are created. This indicates the new release includes database/Clickhouse schema migrations that will run against production before (or alongside) the updated application code. Verify that the migrations in this commit are backward-compatible with the currently running pod version during the rollout window.

The GCP credentials warning on the default_9_12_0 provider is cosmetic and does not affect Kubernetes resource operations.

Resource Changes

    Name                                                       Type                           Operation
~   vpc-native-hourly-notification-cron                        kubernetes:batch/v1:CronJob    update
~   vpc-native-sync-subscription-with-cio-cron                 kubernetes:batch/v1:CronJob    update
~   vpc-native-bg-deployment                                   kubernetes:apps/v1:Deployment  update
~   vpc-native-expire-super-agent-trial-cron                   kubernetes:batch/v1:CronJob    update
~   vpc-native-ws-deployment                                   kubernetes:apps/v1:Deployment  update
~   vpc-native-materialize-yearly-best-post-archives-cron      kubernetes:batch/v1:CronJob    update
~   vpc-native-update-achievement-rarity-cron                  kubernetes:batch/v1:CronJob    update
~   vpc-native-validate-active-users-cron                      kubernetes:batch/v1:CronJob    update
~   vpc-native-calculate-top-readers-cron                      kubernetes:batch/v1:CronJob    update
~   vpc-native-check-analytics-report-cron                     kubernetes:batch/v1:CronJob    update
~   vpc-native-generic-referral-reminder-cron                  kubernetes:batch/v1:CronJob    update
~   vpc-native-worker-job-deployment                           kubernetes:apps/v1:Deployment  update
~   vpc-native-user-profile-analytics-history-clickhouse-cron  kubernetes:batch/v1:CronJob    update
~   vpc-native-update-tags-str-cron                            kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-zombie-user-companies-cron                kubernetes:batch/v1:CronJob    update
~   vpc-native-generate-search-invites-cron                    kubernetes:batch/v1:CronJob    update
~   vpc-native-squad-posts-analytics-refresh-cron              kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-stale-user-transactions-cron              kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-zombie-images-cron                        kubernetes:batch/v1:CronJob    update
~   vpc-native-personalized-digest-deployment                  kubernetes:apps/v1:Deployment  update
~   vpc-native-update-current-streak-cron                      kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-channel-highlights-cron                   kubernetes:batch/v1:CronJob    update
+   vpc-native-api-db-migration-544f4b1c                       kubernetes:batch/v1:Job        create
~   vpc-native-channel-highlights-cron                         kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-zombie-users-cron                         kubernetes:batch/v1:CronJob    update
~   vpc-native-update-source-public-threshold-cron             kubernetes:batch/v1:CronJob    update
~   vpc-native-update-views-cron                               kubernetes:batch/v1:CronJob    update
~   vpc-native-materialize-monthly-best-post-archives-cron     kubernetes:batch/v1:CronJob    update
~   vpc-native-user-posts-analytics-refresh-cron               kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-expired-better-auth-sessions-cron         kubernetes:batch/v1:CronJob    update
+   vpc-native-api-clickhouse-migration-544f4b1c               kubernetes:batch/v1:Job        create
~   vpc-native-channel-digests-cron                            kubernetes:batch/v1:CronJob    update
~   vpc-native-temporal-deployment                             kubernetes:apps/v1:Deployment  update
~   vpc-native-clean-zombie-opportunities-cron                 kubernetes:batch/v1:CronJob    update
~   vpc-native-rotate-daily-quests-cron                        kubernetes:batch/v1:CronJob    update
-   vpc-native-api-db-migration-0b7efa68                       kubernetes:batch/v1:Job        delete
~   vpc-native-update-trending-cron                            kubernetes:batch/v1:CronJob    update
~   vpc-native-user-profile-analytics-clickhouse-cron          kubernetes:batch/v1:CronJob    update
~   vpc-native-update-highlighted-views-cron                   kubernetes:batch/v1:CronJob    update
~   vpc-native-post-analytics-clickhouse-cron                  kubernetes:batch/v1:CronJob    update
~   vpc-native-personalized-digest-cron                        kubernetes:batch/v1:CronJob    update
... and 11 other changes

Copy link
Copy Markdown
Member

@idoshamun idoshamun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We just need to make sure old clients won't break all of a sudden (except when using smart prompts)

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