Release Workflow 2.0.5 - #486
Merged
Merged
Conversation
Member
Author
|
Ready to publish: the full target-branch build for the actual correction a24f8c4 passed, including all MySQL/PostgreSQL shards, MariaDB, coverage ratchet/Codecov, and Laravel 9-13 upgrade cells: https://github.com/durable-workflow/workflow/actions/runs/34067771846 . The release-metadata PR checks also pass. A separate clean Laravel 13 consumer installing published 2.0.4 reproduced the exact pending workflow and MaxAttemptsExceededException with one failed queue job; the same consumer will be upgraded to the new Packagist package for the confirming run. |
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
2 participants
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.
Release metadata and changelog for #485 / #484. The fix prevents early activity/timer delivery from exhausting transport attempts, preserves durable deadlines and business retry budgets, and uses capped fresh timer dispatches. No schema or protocol change. Wait for the full main-branch database/coverage and Laravel upgrade checks on a24f8c4, then merge and publish the new tag. #484 remains open until the published-package reproduction passes.