Repository navigation
Fix scheduled Daf delivery and runtime compatibility in 3.1.1 - #24
Merged
Merged
Conversation
Include the approved igbinary runtime compatibility fix and handle unreachable private settings replies without sending a second DM. Preserve Composer lock, database schema and queued delivery identities.
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.
Scheduled Daf messages failed in MadelineProto's HTML parser when a Hebcal/Sefaria URL contained raw & query separators. This patch separates raw template values from HTML and shares the rich Daf card between private views and scheduled group deliveries, preserving custom entities, media, buttons and topic routing.
Eligible prepared 3.1.0 Daf jobs receive a narrow URL-escaping repair under their existing lease only when never dispatched or rejected by the known local DOM parser error. Frozen content, random_id, attempts/history and expiry are retained; generic uncertain sends and failed/expired jobs are not revived or reset.
The approved igbinary 3.2.16 Docker compatibility fix includes its original source/license and offline initialization probes in CI and the manual release workflow. A private PEER_ID_INVALID no longer causes a second DM: a valid originating group gets a localized private-start link. Group permissions, authorization, other RPC errors and cancellation remain unchanged.
VERSION, CHANGELOG, release notes and current English/Hebrew documentation are updated for 3.1.1. Composer dependencies/lock, database schema/migrations and existing library patches are unchanged. This PR is merged as ae7bdc5; annotated tag v3.1.1 and the release are published after the final commit passed its gates. No production deployment was performed by this PR.
Validation: