ci(radar-export): publish on release-branch catalog pushes; daily schedule - #13736
Merged
Merged
Conversation
…e schedule daily The radar-server only consumes the stable asset, so a catalog merge on the active release branch waited for the Monday 06:17 UTC cron and the feed sat up to a week behind the README (2026-09-14: the Together signup-credit row removed in d6e62ae only left the feed after a manual dispatch). Trigger on release/** pushes for the same catalog paths and move the schedule to 03:17 UTC daily, ahead of the server's 04:23 UTC publish cycle.
muhamadgalihsaputra
pushed a commit
to niyatna/NiyatnaRoute
that referenced
this pull request
Sep 27, 2026
…edule (diegosouzapw#13736) The radar-server only consumes the stable asset, so a catalog merge on the active release branch waited for the Monday 06:17 UTC cron and the feed sat up to a week behind the README (2026-09-14: the Together signup-credit row removed in 52a98ad only left the feed after a manual dispatch). Trigger on release/** pushes for the same catalog paths and move the schedule to 03:17 UTC daily, ahead of the server's 04:23 UTC publish cycle.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
radar-export.ymlonly fired onmainpushes and a Monday 06:17 UTC cron, while the radar-server consumes nothing but the published asset. A catalog change merged on the active release branch therefore waited for the next weekly cron: on 2026-09-14 the Together signup-credit row removed in d6e62ae stayed in the Radar feed until a manualworkflow_dispatchon 2026-09-15.release/**to the push trigger (same catalog/script/workflow path filter). The active release branch is the default branch and is what the cron already exported; the asset is one stable file either way.17 3 * * *(daily 03:17 UTC) so the server'sradar-feed.timerat 04:23 UTC publishes against the same-day export, and provenance stays fresh.No change to the job itself; the concurrency group is per ref, so a release push and a main push do not cancel each other.
Validation
on= workflow_dispatch, push (branchesmain,release/**), schedule (17 3 * * *).release/v3.8.51today published run 34969390566 and the server published feed2026.09.15.2(443 models) from it — the same job this PR now triggers automatically.CI triage (run 34972202323 on 3cf1b85)
The diff is one file,
.github/workflows/radar-export.yml, which is outside the scope of every red job:check:secrets --ratchet(gitleaks oversrc,open-sse,bin,electron,scripts)tests/unit/noauth-model-lockout.test.tsmissing fromstryker.conf.json)isPaidModelTarget, Jina catalog duplicate,persistAttemptLogsstream/redaction, hidePaidModels settings routes,#12150markers,en.jsonkeys