chore: Update version for release (beta) #1199
Merged
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
[email protected]
Patch Changes
14c2bdf: Tasks should now be much more robust and resilient to reconnects during crucial operations and other failure scenarios.
Task runs now have to signal checkpointable state prior to ALL checkpoints. This ensures flushing always happens.
All important socket.io RPCs will now be retried with backoff. Actions relying on checkpoints will be replayed if we haven't been checkpointed and restored as expected, e.g. after reconnect.
Other changes:
MAX_TASK_RUN_ATTEMPTSUpdated dependencies [14c2bdf]
@trigger.dev/[email protected]
Patch Changes
14c2bdf: Tasks should now be much more robust and resilient to reconnects during crucial operations and other failure scenarios.
Task runs now have to signal checkpointable state prior to ALL checkpoints. This ensures flushing always happens.
All important socket.io RPCs will now be retried with backoff. Actions relying on checkpoints will be replayed if we haven't been checkpointed and restored as expected, e.g. after reconnect.
Other changes:
MAX_TASK_RUN_ATTEMPTS@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
Patch Changes
@trigger.dev/[email protected]
@trigger.dev/[email protected]
@trigger.dev/[email protected]
@trigger.dev/[email protected]
@trigger.dev/[email protected]
Patch Changes
14c2bdf: Tasks should now be much more robust and resilient to reconnects during crucial operations and other failure scenarios.
Task runs now have to signal checkpointable state prior to ALL checkpoints. This ensures flushing always happens.
All important socket.io RPCs will now be retried with backoff. Actions relying on checkpoints will be replayed if we haven't been checkpointed and restored as expected, e.g. after reconnect.
Other changes:
MAX_TASK_RUN_ATTEMPTS