September 2026
Check out what's new for Venue.sh! New features, updates, bug fixes—it's all here!
DORA webhooks for repositories
23 September release
Development Insights adds per-repository DORA webhooks so external CI/CD and incident tools can push deployment, incident, and pull request events into Venue.sh. Events are validated, rate-limited, and forwarded to DevLake so your DORA dashboard stays current.
Repository-scoped setup - Editors and admins create one webhook per repository from Development Insights or from Sync Status via Manage Webhooks.
One-time credentials - Venue.sh shows the bearer credential once at creation or rotation. Copy it into your pipeline; it cannot be retrieved again.
Lifecycle management - Rename, retry provisioning, rotate, revoke, or delete a webhook from the repository configuration screen. Demo users can view webhooks but cannot change them.
Ingest endpoints - Authenticated POST endpoints accept deployment, incident, and pull request payloads from tools such as Jenkins, GitHub Actions, or custom scripts.
After a webhook is active, point your pipeline at the ingest URL and send events for the repository. DORA metrics on the DORA dashboard populate from the forwarded data.
See Development Insights and Sync Status for enabling metrics collection and tracking pipeline health.
Template launches and menus
23 September release
Template launches - When a software template launch succeeds, the tasks list updates without reloading the page.
Menu typography - Dropdown and profile menus across the portal use 14px body text so they match the rest of the dashboard.
See Templates to browse and launch software templates.
OAuth for MCP servers
14 September release
Some MCP servers will not run a tool until you sign in with the provider. Venue.sh reads the server's protected-resource metadata on a 401, registers an OAuth client for you, and lets each user connect their own account. No client ID or secret to paste in.
- Automatic discovery - Register a URL-based MCP server and Venue.sh handles dynamic client registration when OAuth is required.
- Inline connect in chat - The Assistant calls a tool you are not authorized for yet? An inline card opens a popup. Authorize there and the tool call picks up where it left off. You do not resend the message.
- Reconnect when expired - Expired tokens get Reconnect your account, not a silent failure.
- My connections - lists every OAuth MCP server you linked, its status, and when access expires. Connect, reconnect, or disconnect from one screen.
Once a server is registered and you are connected, try:
- "What Jira issues are assigned to me this sprint?"
- "Search Confluence for our deployment runbook."
See MCP Servers to register servers and Assistant for chat workflows.
Bulk repository ingestion
14 September release
Ingestion, embeddings, and summaries no longer run inside dashboard HTTP requests. Backend workers own the job queue now. They retry failed repos, cap concurrency, and keep going when one repository fails.
- Bulk runs - Kick off ingestion for many repositories in one job. Watch overall progress while each repo succeeds or fails on its own.
- Skip unchanged repos - If the content digest matches the last run, Venue.sh marks the job skipped. Force a re-ingest when you want a fresh index anyway.
- Background workers - GitIngest jobs batch by Git connection, credentials stay isolated per batch, and results land in storage so search, summaries, and Skills discovery keep working while the queue drains.
Import and entity updates still trigger ingestion the same way as before. See AI Settings. The difference is you can queue hundreds of repos and close the tab.
Users table fixes
14 September release
Last Signed In was blank for everyone. The API still returned an empty string left over from a previous migration. It now reads each user's most recent session in the active organization.
Sorting by Joined or Last Signed In also did nothing before. Both columns reorder the table now.
See Users and Teams for inviting and managing people.
Other fixes
14 September release
- Active devices - listed nothing after your session passed Better Auth's 24-hour freshness check, even though you were still signed in for a week. The page now reads unexpired sessions from the database. If the fetch fails, you get an error instead of an empty section.
- Docs Hub titles and errors - TechDocs pages no longer flash an opaque database ID as the title while loading. When docs are missing, the message says whether the entity was not found or the entity exists but has no TechDocs content configured yet.