Angaben zum Datum
Datum aus der Quelle.
Erstmals gesehen am .
Inngest 1.46.0: Sandbox-Secrets, Cloud-Sandboxes und API-Keys mit Berechtigungen
Inngest 1.46.0 ermöglicht die Auswahl gespeicherter Sandbox-Secrets per Namensliste, deren Verwaltung im Dashboard samt .env-Import, experimentelle Cloud-Sandboxes aus der lokalen Entwicklung via inngest login, API-Keys mit feingranularen Berechtigungen für die v2 API, CLI und MCP sowie benutzerdefinierte Concurrency-Keys in Traces.
Release Notes
#4864 feat(api): add sandbox secret name arrays
Sandbox creation supports selecting stored secrets with
secrets: ["OPENAI_API_KEY"]and injecting each under that same name.#4876 feat(dashboard): manage sandbox secrets in the sidebar
Manage sandbox secrets from the dashboard, including importing
.envfiles into editable rows.#4886 feat(dev): connect local workflows to Cloud sandboxes
Experimental Cloud sandboxes from local development using
inngest login, without deploying an app or configuring an SDK sandbox token.#4891 feat(dashboard): add api keys with permissions
Admins can create API keys with fine-grained permissions for the v2 API, CLI, and MCP. Keys can expire or stay valid until revoked. Existing api and signing keys keep working unless an admin disables legacy key access.
#4915 feat(tracing): include custom concurrency keys in spans
Custom concurrency expressions and evaluated values are available in run and execution traces and through the run trace GraphQL API. Values longer than 512 characters are truncated in traces.
#4918 feat(queue): accept bounded direct item hints …