Repository navigation
Release v2.5.0 - #343
Merged
Merged
Release v2.5.0#343
Conversation
… (PRs #277-#342) The forwarder's execution moves out of the Python core and into the Go worker. The Go engine owns the whole delivery decision and its pipeline: execution engine and Telegram runtime boundary (#284), PostgreSQL persistence and the real rule store (#286), bot transport, branding stage and durable scheduler (#288), canonical content policy, link classifier and codepoint length parity (#290), Go transform authority - cleaner, links, replacements (#293) with target-scoped overrides (#294), header placeholder rendering (#295), the paid-addon entitlement gate (#296), filter tenant boundaries (#302), forward-every-N cadence (#310), the dedup plane (#309), routing and loop prevention (#308), the effective-settings ownership layer (#311), the AI provider execution path (#313), channel-to-channel AI rewriting (#314), the PVA/autoreply port (#315) with structured decision logging (#320, #318), and the AI rewrite stage wired into the production worker main (#325). The core serves the Telegram transport gateway in-process (#321) and ships the proto stubs and runtime the worker resolves (#322, #323). Delivery guarantees are verified end to end with observability correlation (#312). Delivery reliability got its root causes fixed instead of patched around: re-upload staging now carries the real file extension - the PHOTO_EXT_INVALID root cause (#339), and one dispatch per job - fence lease, album ambiguity, bot-route media rescue, staged-file hygiene (#341). Poll cursors release past terminal gaps (#278), failures land in a canonical taxonomy with raw Telegram error capture (#279), and empty-session probe semantics plus the missing SendMedia RPC are in (#330). The lane-roster claim makes the queue 5-7x faster at backlog scale (#328). The web dashboard becomes a premium application: application shell, design system, task workspace and delivery timeline (#316, #280, #281), the DevOps flight deck (#282, #283) with working worker controls (#335-#338), logging-pipeline health (#317), task monitor sort and needs-attention filter (#332), throughput aggregation windows (#333), and poll backoff with stale-data labelling (#331). The branding/replace/AI suite upgrades end to end (#342): the channel-only hop gate (a user message ships direct with its own "Forwarded from" header, channel content takes the branded hop), replace any link / any @id maps with entity-aware rewriting on both engines, the prompt library with enable/disable across bot, dashboard and mobile, the branding failure trail into the Rust log store, and 1:1 i18n across all ten locales. Ops: deploy actually ships the worker (#340), percentile accessors, Postgres ops-store CI and the worker master key (#329), compose overlay tests (#326), truthful stage health with correlation on every sink, and the architecture/behavior contract is documented (#289, #277).
Codex Review Summary: ❌ FailedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
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.
Version 2.5.0
Bumps
VERSION2.4.0 → 2.5.0 andmobile/pubspec.yaml2.4.0+10 → 2.5.0+11.What ships in 2.5.0
Everything merged to
mastersince v2.4.0 (PRs #277–#342). Headlines:Release mechanics
masterat the release commit; pushing thev2.5.0tag on it then triggersrelease.yml(single-fileatfbinaries for Linux/macOS/Windows on x86_64+arm64, static Go API binaries, multi-arch Docker images, source tarball, SHA256SUMS, GitHub Release).docs/openapi.yamlstays at1.0.0— that is the API contract version, unchanged by the route parity audit.