-
-
Notifications
You must be signed in to change notification settings - Fork 791
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: triggerdotdev/trigger.dev
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 5b40c44
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: triggerdotdev/trigger.dev
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 96243ef
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 4 commits
- 10 files changed
- 2 contributors
Commits on Aug 22, 2025
-
Configuration menu - View commit details
-
Copy full SHA for c16cc57 - Browse repository at this point
Copy the full SHA c16cc57View commit details -
fix(v3): eagerly dequeue messages from a queue when that queue is add…
…ed to or removed from (v4 backport) (#2438) * fix(v3): eagerly dequeue messages from a queue when that queue is added to or removed from (v4 backport) * fixed configuration
Configuration menu - View commit details
-
Copy full SHA for 5e4756f - Browse repository at this point
Copy the full SHA 5e4756fView commit details -
fix(v3): prevent saturated queues from dominating dequeue attempts by…
… adding a cooloff period of successive failed dequeues (#2439) * fix(v3): prevent saturated queues from dominating dequeue attempts by adding a cooloff period of successive failed dequeues * Add env vars and add a marqs shutdown on SIGTERM/INT
Configuration menu - View commit details
-
Copy full SHA for ad26cde - Browse repository at this point
Copy the full SHA ad26cdeView commit details -
* Add MCP Server documentation to documentation site This change introduces comprehensive documentation for the Trigger.dev MCP Server, covering its installation, usage, and available tools. The addition is necessary to provide users with detailed guidance on leveraging the MCP Server for managing Trigger.dev projects, tasks, and deployment processes. - Updated `docs.json` to include a new section for the MCP Server documentation, improving navigation and accessibility. - Added `mcp-introduction.mdx` as an introductory guide to the MCP Server, detailing its purpose and installation steps. - Included `mcp-tools.mdx`, a document outlining each tool available in the MCP Server, complete with descriptions and example usages. - The new content is aimed at improving user understanding and efficiency in using Trigger.dev's MCP Server capabilities. * Refactor MCP installation documentation The changes were necessary to streamline the MCP installation guidance and align our documentation with the latest client support capabilities. Removing the manual installation section and redundant information helps reduce confusion for users. - Updated installation instructions to lead with auto-configuration for supported clients. - Cleaned up the options and examples sections to enhance clarity. - Reformatted client configuration details for better readability. - Removed outdated links in the "Next Steps" section, focusing on more direct resources such as available MCP tools. * mcp docs edits * Add debugMode to get_run_details * add cancel_run * Add list deployments tools * Add list preview branches tool * Docs: adds agent rules page * Adds redirect for the CLI path to work * Adds subagent install image --------- Co-authored-by: James Ritchie <james@trigger.dev>
Configuration menu - View commit details
-
Copy full SHA for 96243ef - Browse repository at this point
Copy the full SHA 96243efView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 5b40c44...96243ef