chore: Update version for release (beta) #1057
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}
github-actions
bot
force-pushed
the
changeset-release/main
branch
5 times, most recently
from
964195f to
98ffc93
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
98ffc93 to
ed1cd16
Compare
ericallam
approved these changes
Apr 24, 2024
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
@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
b68012f: Make msw a normal dependency (for now) to fix Module Not Found error in Next.js.
It turns out that webpack will "hoist" dynamically imported modules and attempt to resolve them at build time, even though it's an optional peer dep:
https://x.com/maverickdotdev/status/1782465214308319404
b68012f: Move to our global system from AsyncLocalStorage for the current task context storage
b68012f: Extracting out all the non-SDK related features from the main @trigger.dev/core/v3 export
Updated dependencies [b68012f]
Updated dependencies [b68012f]
@trigger.dev/[email protected]
@trigger.dev/[email protected]
@trigger.dev/[email protected]
@trigger.dev/[email protected]
@trigger.dev/[email protected]
Patch Changes