fix(feed): use channel_v1 config for channel feed

[idoshamun]

Summary

• update FeedConfigName.Channel from channel to channel_v1 in the feed integration types
• keep channelFeed generator/test behavior unchanged by continuing to reference the enum value

Key decision

• fix the naming mismatch at the source in daily-api so feed_config_name matches the loaded daily-feed key (channel_v1) and avoids fallback to engagement-ranked config

Closes ENG-955

---

Created by Huginn 🐦‍⬛

[pulumi]

🍹 The Update (preview) for dailydotdev/api/prod (at 1a8b8c6) was successful.

✨ Neo Explanation

This is a standard application deployment rolling out a new build across all API services, workers, and cron jobs, accompanied by the routine creation of database and ClickHouse migration jobs for the new version.

Root Cause Analysis

A new version of the API application has been built and is being deployed to production. Every workload in the cluster (deployments and cron jobs) references the container image by version tag, so a new build triggers a fleet-wide rollout to the updated image.

Dependency Chain

The new application version cascades uniformly across all resources:

1. 7 long-running Deployments (API, background workers, WebSocket server, private API, Temporal, personalized digest, worker jobs) are being updated to pull the new container image.
2. 34 CronJobs are being updated to reference the new image so future scheduled runs use the new code.
3. 2 one-time migration Jobs (database and ClickHouse) are being replaced: the old version's migration jobs are deleted and new ones for the current version are created. This is the normal pattern — migration jobs are named after the version they belong to, so each deployment creates fresh jobs and cleans up the prior version's jobs.

Risk analysis

No stateful resources (databases, storage, persistent volumes) are being modified or deleted. The migration jobs (both DB and ClickHouse) involve schema changes, but they run as one-time Kubernetes Jobs against existing databases — the migrations themselves carry inherent risk, but that is expected behavior for this deployment pattern. Kubernetes Deployments use rolling updates by default, so downtime is not expected for the running services.

Resource Changes

    Name                                                       Type                           Operation
~   vpc-native-post-analytics-history-day-clickhouse-cron      kubernetes:batch/v1:CronJob    update
~   vpc-native-worker-job-deployment                           kubernetes:apps/v1:Deployment  update
~   vpc-native-user-profile-updated-sync-cron                  kubernetes:batch/v1:CronJob    update
~   vpc-native-update-current-streak-cron                      kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-stale-user-transactions-cron              kubernetes:batch/v1:CronJob    update
~   vpc-native-update-views-cron                               kubernetes:batch/v1:CronJob    update
~   vpc-native-update-tag-recommendations-cron                 kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-zombie-users-cron                         kubernetes:batch/v1:CronJob    update
~   vpc-native-personalized-digest-cron                        kubernetes:batch/v1:CronJob    update
~   vpc-native-update-trending-cron                            kubernetes:batch/v1:CronJob    update
~   vpc-native-check-analytics-report-cron                     kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-gifted-plus-cron                          kubernetes:batch/v1:CronJob    update
~   vpc-native-calculate-top-readers-cron                      kubernetes:batch/v1:CronJob    update
+   vpc-native-api-db-migration-5296d14e                       kubernetes:batch/v1:Job        create
~   vpc-native-post-analytics-clickhouse-cron                  kubernetes:batch/v1:CronJob    update
~   vpc-native-daily-digest-cron                               kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-zombie-opportunities-cron                 kubernetes:batch/v1:CronJob    update
~   vpc-native-update-achievement-rarity-cron                  kubernetes:batch/v1:CronJob    update
~   vpc-native-ws-deployment                                   kubernetes:apps/v1:Deployment  update
~   vpc-native-update-highlighted-views-cron                   kubernetes:batch/v1:CronJob    update
~   vpc-native-agents-digest-cron                              kubernetes:batch/v1:CronJob    update
~   vpc-native-user-profile-analytics-clickhouse-cron          kubernetes:batch/v1:CronJob    update
~   vpc-native-user-profile-analytics-history-clickhouse-cron  kubernetes:batch/v1:CronJob    update
~   vpc-native-personalized-digest-deployment                  kubernetes:apps/v1:Deployment  update
~   vpc-native-validate-active-users-cron                      kubernetes:batch/v1:CronJob    update
~   vpc-native-deployment                                      kubernetes:apps/v1:Deployment  update
~   vpc-native-temporal-deployment                             kubernetes:apps/v1:Deployment  update
~   vpc-native-clean-zombie-images-cron                        kubernetes:batch/v1:CronJob    update
~   vpc-native-update-source-tag-view-cron                     kubernetes:batch/v1:CronJob    update
+   vpc-native-api-clickhouse-migration-5296d14e               kubernetes:batch/v1:Job        create
~   vpc-native-update-tags-str-cron                            kubernetes:batch/v1:CronJob    update
~   vpc-native-bg-deployment                                   kubernetes:apps/v1:Deployment  update
~   vpc-native-user-posts-analytics-refresh-cron               kubernetes:batch/v1:CronJob    update
-   vpc-native-api-db-migration-ffafce66                       kubernetes:batch/v1:Job        delete
~   vpc-native-generate-search-invites-cron                    kubernetes:batch/v1:CronJob    update
~   vpc-native-expire-super-agent-trial-cron                   kubernetes:batch/v1:CronJob    update
~   vpc-native-sync-subscription-with-cio-cron                 kubernetes:batch/v1:CronJob    update
~   vpc-native-private-deployment                              kubernetes:apps/v1:Deployment  update
~   vpc-native-update-source-public-threshold-cron             kubernetes:batch/v1:CronJob    update
~   vpc-native-squad-posts-analytics-refresh-cron              kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-zombie-user-companies-cron                kubernetes:batch/v1:CronJob    update
... and 5 other changes