Update dependency @workflow/world to v5.0.0-beta.27 - autoclosed - #160
Closed
renovate[bot] wants to merge 1 commit into
Closed
Update dependency @workflow/world to v5.0.0-beta.27 - autoclosed#160renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
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.
This PR contains the following updates:
5.0.0-beta.25→5.0.0-beta.27Release Notes
vercel/workflow (@workflow/world)
v5.0.0-beta.27Minor Changes
#3390
600b096Thanks @alangenfeld! - Add a bounded batch analytics event lookup for enriching canonical event pages.#3365
7683130Thanks @TooTallNate! - Resilient step dispatch: newly created steps are published to the queue in parallel with theirstep_createdevent write, with the serialized input carried on the message (stepInput) so the consumer re-ensures the event if the direct write failed transiently — mirroring resilient start (runInput) and resilient hook resume (hookInput). Worlds that enforce the precondition guard keep the sequential create-then-publish dispatch (only sequencing gives the message a happens-after edge over the create's guard verdict); step-dispatch idempotency keys are now step-identity-scoped. Disable viaWORKFLOW_RESILIENT_STEP_DISPATCH=0.Patch Changes
#3519
dc85865Thanks @VaguelySerious! - Remove thepreconditionGuardWorld capability. A stale replay-context write no longer needs to be rejected: a reader holds a prefix of the log, replay is deterministic on a prefix, and the writer's next write reports the events it was pushed past.#3381
efbc408Thanks @VaguelySerious! - Ignore duplicate events that a concurrent replay wrote for an entity the event log already records, instead of failing the run with a corrupted event log#3437
a0ccfe0Thanks @karthikscale3! - Add OTEL telemetry for hook-triggered time-to-resume:workflow.resume.total_msplus a non-overlapping phase breakdown, on the first durable step after a resume.#3542
de2a86cThanks @VaguelySerious! - Breaking: New runs are created at spec version 6, and a World that declares an older spec version is now rejected before the first run rather than failing partway through one.#3519
dc85865Thanks @VaguelySerious! - Require every event id the runtime reads to be a log position.requireEventSlotreplaces the lenient decode that returned "no position" for an id that is not a slot.#3519
dc85865Thanks @VaguelySerious! - Slot-numbered event ids are a requirement of the World contract, not a capability. TheslotEventIdsflag is gone, and the conformance suite now fails a World whose event ids are not positions.#3479
b589460Thanks @VaguelySerious! - Replay-context event writes now always report the log position they replayed from, and theWORKFLOW_PRECONDITION_GUARDflag is removed.v5.0.0-beta.26Minor Changes
439a495Thanks @karthikscale3! - Carry the run's pinned deployment on lazy resume messages so misrouted deliveries re-route before thehook_receivedwrite.Patch Changes
#3385
74dbf81Thanks @NathanColosimo! - Retry replay timeouts through normal queue redelivery instead of exiting the process, and keep Postgres jobs retryable through Core's terminal delivery limit.#3382
a8db185Thanks @VaguelySerious! - Fold new events returned byevents.createinto the replay log so a completed wait no longer needs a follow-upevents.listround trip#3389
6786db9Thanks @VaguelySerious! - Breaking: SpecVersion 6: Event IDs are now a dense per-run slot number, allocated by the world at publish time so a rejected write leaves no gap in the event log. A replay tells the world how many events it had read and gets back the ones it did not see, so an event that arrives from outside the replay and lands ahead of an event the replay wrote no longer fails the run withCORRUPTED_EVENT_LOG: it is held for whichever part of the workflow awaits it. A gap in the numbering fails the run instead of being replayed over.#3205
22349e9Thanks @NathanColosimo! - Load replay-event suffixes through one World request.#3124
65139acThanks @NathanColosimo! - Infer required run and step entities, including their start times, fromevents.createrequest types.Configuration
📅 Schedule: (in timezone Europe/Rome)
* 0-6 * * 6,0)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.