github-featured/triggerdotdev--trigger.dev

Files

T

Eric Allam 395abe1b92 v3: Various fixes to support papermark use-case (#970 )

* Adding a changeset for v3

* Add a version field to @trigger.dev/core-apps package.json

* Build trigger.dev when doing a prerelease

* bundle @trigger.dev/core-apps with trigger.dev cli

* Fix the init command config template

* Don’t use * for the @trigger.dev/core dep version specifier

* strip workspace: from the package version before installing it

* Added dependenciesToBundle config option to bundle ESM only packages

* Added logging around resolving dependency paths

* Try again

* Resolve dependencies based on the project dir first

* flip the bundled default

* Adding some logs around dev task completion notifications

* Adding some additional logs

* Add more logs

* Write out the log using process.stdout

* Store pending completion notifications and resume them when awaited (fixes race condition)

* Cleanup some of the logs

* Copy over the postinstall step from the projects package.json

* Add support for including additional files when deploying (e.g. prisma schema)

* Don’t run scripts when resolving deps

* copy all the files just in case anything is needed in postinstall

* Remove duplicate option

* Use the tag when outputting the dev command

* Remove the postinstall script

* add the trigger dir to the config if the default is not chosen

* Remove the “hud” display in the dev command

* trigger file names with dashes now work

* Better file watching in dev

* Much better duplicate ID experience now

* Much better “Project not found” error

* Export the handleError function types from sdk

* Add support for configuring instrumentation

* Upgrade and unify @opentelemetry/* packages (and remove storybook from the webapp)

* Fix typescript error in react package

* Upgrade react types in webapp

* Allow span icons to be determined based on the span name (e.g. prisma:)

* Ignore built-in env vars when checking for env vars, and allow continuing the deployment even if missing env vars were detected

* Improve the retry.fetch default behavior and option structure

* Fixed typescript errors with packages/email react types

* Update the retry.fetch docs

2024-03-25 17:02:49 +00:00

2.0 KiB

Raw Permalink Blame History

Changesets

Trigger.dev uses changesets to manage updated our packages and releasing them to npm.

Adding a changeset

To add a changeset, use pnpm run changeset:add and follow the instructions here. Please only ever select one of our public packages when adding a changeset.

Release instructions (local only)

Based on the instructions here

Run pnpm run changeset:version
Run pnpm run changeset:release

Release instructions (CI)

Please follow the best-practice of adding changesets in the same commit as the code making the change with pnpm run changeset:add, as it will allow our release.yml CI workflow to function properly:

Anytime new changesets are added in a commit in the main branch, the release.yml workflow will run and will automatically create/update a PR with a fresh run of pnpm run changeset:version.
When the version PR is merged into main, the release.yml workflow will automatically run pnpm run changeset:release to build and release packages to npm.

Pre-release instructions

Add changesets as usual pnpm run changeset:add
Switch to pre-release mode by running pnpm run changeset:next
Create version pnpm run changeset:version
Release pnpm run changeset:release
Switch back to normal mode by running pnpm run changeset:normal

Snapshot instructions

!MAKE SURE TO UPDATE THE TAG IN THE INSTRUCTIONS BELOW!

Add changesets as usual

pnpm run changeset:add

Create a snapshot version (replace "prerelease" with your tag)

pnpm exec changeset version --snapshot prerelease

Build the packages:

pnpm run build --filter "@trigger.dev/*" --filter "trigger.dev"

Publish the snapshot (replace "dev" with your tag)

pnpm exec changeset publish --no-git-tag --snapshot --tag prerelease

2.0 KiB Raw Permalink Blame History