Zum Inhalt springen

Inngest Release Notes

14 Einträge aus 1 Quelle. Zuletzt aktualisiert:

Folge Inngest, um die Release Notes in deinen Feed zu holen.

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Inngest

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 .env files 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 …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Inngest

Inngest 1.45.1: Bessere CLI-Meldung und Verwerfen nicht routbarer Queue-Items

Inngest 1.45.1 verbessert die Meldung bei nicht angemeldeter CLI und verwirft dauerhaft nicht routbare Queue-Items, sofern Konsumenten dafür WithPermanentConstraintErrorHandler konfigurieren.

Migration Notes

  • #4878 fix(queue): drop permanently unroutable items

    Consumers must explicitly configure WithPermanentConstraintErrorHandler to enable dropping; existing behavior is unchanged otherwise.

Changelog

🐛 Bug Fixes

  • (cli) Better message when cli is unauthed (#4883)
  • (queue) Drop permanently unroutable items (#4878)

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Inngest

Inngest 1.45.0: OAuth-Login für CLI und Cloud-MCP-Clients

Inngest 1.45.0 bringt OAuth-Login für die CLI (inngest login, inngest auth status, inngest logout) und OAuth-Authentifizierung für Cloud-MCP-Clients und behebt mehrere Fehler bei Debounce, Sandbox-Uploads und REST-v2-Fehlermeldungen.

Release Notes

  • #4780 feat(auth): add cli oauth login

    Adds cloud login support to the Inngest CLI. OAuth credentials are stored in the operating system’s credential store and refreshed automatically.

    # log in
    inngest login
    
    # check the current session
    inngest auth status
    
    # start a new login and replace the current session
    inngest login --force
    
    # revoke the session and remove local credentials
    inngest logout
    
  • #4781 feat(auth): add mcp oauth support

    Inngest Cloud MCP clients can now authenticate via OAuth. Users can now select the account, permissions, environment access, etc. in the Inngest Dashboard.

  • #4788 fix(debounce): handle removed config during execution

    Prevent debounce timeout execution from crashing after debounce configuration is removed from a function.

  • #4789 fix(api): serialize sandbox bytes written as a number

    Sandbox file upload responses now serialize bytesWritten as a number instead of a string.

  • #4813 fix(api): normalize unknown REST v2 body field errors

    REST v2 now returns a clear invalid_request error when a JSON request body contains a field unsupported by the server. …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Inngest

Inngest 1.44.0: Scores in der Run-Timeline und KI-Nutzungsübersicht

Inngest 1.44.0 zeigt erfasste Scores als Badge in der Run-Timeline und eine Run-weite KI-Nutzungsübersicht (Tokens, Kosten, Modelle) an und behebt überlappende Steps bei Key-Queues mit Concurrency-Limit 1.

Release Notes

  • #4736 feat(scores): show recorded scores on timeline bars

    Scores recorded on a step now appear as a badge on that step's bar in the run timeline, with a hover card listing each score and its value.

  • #4758 feat(ai): add run-level AI usage summary

    None (user-facing note on the UI PR).

  • #4759 feat(ui): show run AI usage summary

    Run details now show a run-level AI usage summary (total tokens, cost, models used).

  • #4766 fix(queue): renew capacity leases before dispatch

    Fixed an issue where steps using key queues could overlap despite a concurrency limit of one when a pre-acquired capacity lease expired before its first renewal.

Migration Notes

Changelog

🚀 Features

  • (ai) Add run-level AI usage summary (#4758)
  • (ui) Show run AI usage summary (#4759)
  • (scores) Show recorded scores on timeline bars (#4736)

🐛 Bug Fixes

  • (queue) Renew capacity leases before dispatch (#4766)
  • (insights) Fix broken download with invalid dates (#4769)
  • (connect) Track reply delivery outcomes (#4774) …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Inngest

Inngest 1.43.0: Functions-Tabelle nach App filtern

Inngest 1.43.0 ermöglicht das Filtern der Functions-Tabelle im Dashboard nach App und ergänzt einen CLI-User-Agent für API-Analysen.

Release Notes

  • #4199 feat(dashboard): add app filtering to functions table

    Users can now filter functions by app in the Functions table, making it easier to find functions belonging to specific apps.

Migration Notes

Changelog

🚀 Features

  • (cli) Add cli user agent for api analytics (#4752)
  • (dashboard) Add app filtering to functions table (#4199)

🐛 Bug Fixes

  • (ci) Add --force-with-lease to the Sync Staging workflow push (#4629)

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Inngest

Inngest 1.42.0: Scores und Experiments im Dev-Server, Endpunkt POST /v2/events

Inngest 1.42.0 ergänzt im Dev-Server Seiten für Scores und Experiments, zeigt geplante Ausführungszeiten im Dashboard an, fügt einen v2-Endpunkt POST /v2/events zum Senden von Events hinzu und behebt hängende Run-Listen auf großen Postgres-Deployments.

Release Notes

  • #4697 feat(improvement): Add-scores-and-experiments-empty-states-to-dev-server

    The dev server now includes Scores and Experiments pages (AI section, beta) showing how to get started with step.score() and group.experiment(). Data for these features is displayed in Inngest Cloud after deploying; the dev server pages let you register interest in local support.

  • #4718 fix(traces): scope span self-join by run_id

    Fixed the runs list hanging on large Postgres deployments when deferredFrom/isDeferred was selected. No migration or manual index needed.

  • #4720 feat: Surface event scheduling in the dashboard

    • Surface scheduled at in the dashboard's run's page iff the event is scheduled in the future
  • #4721 refactor(runs): remove legacy tokens from run output header

    Removed Model/token values parsed from step.run output in favor of a nudge towards the better AI metadata setup.

  • #4724 feat(api): add v2 send event endpoint

    Added a send event endpoint to the v2 rest api, cli and mcp.

    POST /v2/events

    inngest api --prod send-event \
      --name "app/user.created" \
      --data '{"userId":"user_123","email":"ada@example.com"}' \
      --id "user-created-user_123"
    ``` …
    

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Inngest

Inngest 1.41.0: Robustere Queue-Operationen und KI-Dashboard

Inngest 1.41.0 macht Queue-Operationen robust gegenüber nicht verfügbaren Shards, ergänzt ein Insights-basiertes KI-Dashboard und behebt Fehler bei Connect-Verbindungsstatus und Lease-Erneuerung.

Release Notes

  • #4688 fix(queue): isolate unavailable shards

    Queue operations spanning multiple shards now tolerate unavailable shards and continue returning results from healthy shards. Shard-group workers also continue trying healthy lease candidates when another shard is unavailable.

Changelog

🚀 Features

  • (ai-overview) Add insights-backed AI dashboard (#4662)
  • (ui) Nudge metadata usage in run details (#4683)

🐛 Bug Fixes

  • (connect) Prevent connection state regression during gateway draining (#4685)
  • (queue) Isolate unavailable shards (#4688)
  • (connect) Make lease renewal idempotent after lost ACKs (#4687)

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Inngest

Inngest 1.40.0: MCP-Tools aus REST API v2 und Endpunkt zum Auflisten von Apps

Inngest 1.40.0 erzeugt die MCP-Tools des Dev-Servers aus der REST API v2, ergänzt einen v2-Endpunkt zum Auflisten von Apps und behebt Fehler bei Ausdrücken mit falsy Ternaries und bei Queue-Fehlerprüfungen.

Release Notes

  • #4674 feat(mcp): generate mcp tools from rest api v2

    Updates dev server mcp tools list to expose more tools that align more closely with the v2 rest api and cli

Changelog

🚀 Features

  • (mcp) Generate mcp tools from rest api v2 (#4674)
  • (api) Add v2 apps list endpoint (#4657)

🐛 Bug Fixes

  • (epxressions) Add support for falsy terns (#4676)
  • (queue) Correct reversed errors.Is arguments for ErrQueueItemNotFound (#4679)

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Inngest

Version 1.39.0: Runs abbrechen und ab bestimmtem Step erneut ausführen

Inngest 1.39.0 fügt der REST API v2 und der CLI das Abbrechen von Runs sowie das erneute Ausführen ab einem bestimmten Step hinzu und ändert die Schnittstelle für Queue-Scanner (Run(ctx, runtime)).

Release Notes

  • #4638 feat(api): v2 api cancel run

    Adds cancel run to the v2 rest api and cli.

    POST /api/v2/runs/{run_id}/cancel

    inngest api POST /api/v2/runs/{run_id}/cancel

  • #4645 feat(api): rest v2 rerun from step

    POST /v2/runs/{run_id}/rerun

    with payload:

    {
      "fromStep": {
        "stepId": "fetch-user",
        "input": [
          {
            "userId": "user_123"
          }
        ]
      }
    }
    

    CLI equivalent:

    inngest api --prod rerun <run_id> \
      --from-step "step 2" \
      --input '[{"foo":"bar"}]'
    

Migration Notes

  • #4655 refactor(queue): add shard scanner boundary

    None

    Validation

    • go test -count=1 ./pkg/execution/queue
    • go test -run '^$' ./pkg/execution/state/redis_state
  • #4665 refactor(queue): add scanner runtime

    Out-of-tree queue scanner implementations must update Run(ctx, dispatch) to Run(ctx, runtime), use runtime.Dispatch to submit leased work, and may inspect runtime.WorkerSemaphore before scanning. Implementations that call DispatchFunc must handle the returned DispatchedItem; callers may ignore it, or wait on Done() with context cancellation or a timeout. …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Inngest

Version 1.38.1: Klarere Befehle und Doku zum Auflisten von Runs

Inngest 1.38.1 verdeutlicht die Befehle und Dokumentation zum Auflisten von Runs in der API.

Changelog

🐛 Bug Fixes

  • (api) Clarify run list commands and docs (#4647)

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Inngest

Version 1.38.0: Beta v2-Endpunkte für Runs, Limit von einem Jahr für sleep

Inngest 1.38.0 fügt beta v2-Endpunkte zum Auflisten von Runs hinzu, begrenzt sleep und wait-for-event auf höchstens ein Jahr (sonst InngestErrTimeoutTooLong) und korrigiert Reihenfolge und Queue-Zeit asynchroner Opcodes bei aktiviertem Checkpointing.

Release Notes

  • #4608 fix: fix the ordering and queue time of async opcodes

    Fix the ordering and display of queueing delay for invoke, sleep, waitForEvent, waitForSignal, and Promise.all when checkpointing is on

  • #4621 feat(api): add v2 runs list endpoints

    Adds beta v2 REST endpoints for listing function runs:

    • GET /v2/runs
    • GET /v2/apps/{appId}/functions/{functionId}/runs

    Supports cursor pagination, time ranges and fields, status, public app/function IDs, deferred-run filters, ordering, and optional outputs.

  • #4628 feat: enforce one-year maximum duration for sleep and wait-for-event

    Inngest now enforces a maximum duration of one year for sleep operations and wait-for-event timeouts. Attempting to schedule a sleep or wait beyond one year will result in an InngestErrTimeoutTooLong error.

Migration Notes

Changelog

🚀 Features

  • (dashboard) Add Sandboxes waitlist (#4611)
  • (queue) Define grpc service interfaces for queue producer and consumer (#4610)
  • (queue) Route RequeueByJobID through producer (#4613)
  • Enforce one-year maximum duration for sleep and wait-for-event (#4628) …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Inngest

Version 1.37.0: v2-Endpunkt für Scores und bessere Fehlermeldungen

Inngest 1.37.0 ergänzt einen v2-REST-Endpunkt POST /v2/runs/{runId}/scores zum Erfassen von Scores, verbessert Fehlermeldungen bei Antworten, die nicht vom SDK stammen, und zeigt fehlgeschlagene Versuche ohne Step als „Function Error“ an.

Release Notes

  • #4453 feat(api): add v2 score endpoint

    Adds a v2 REST scoring endpoint for recording named scores against a function run or individual steps in a run. This

    POST /v2/runs/{runId}/scores

    with body:

    [
      {
        "name": "accuracy",
        "value": 0.95,
       "stepId": "step 1"
      }
    ]
    

    Scores are run scoped when stepId is omitted. Score values can be a number or boolean. Scores can be submitted in batches of up to 100. Experiment scores are supported at run level only (I copied this from the sdk, shout if we don't want to support this in the api) like so:

    [
      {
        "name": "accuracy",
        "value": 0.95,
        "experiment": {
          "id": "model-routing",
          "variant": "baseline"
        }
      }
    ]
    
  • #4566 fix(execution): improve copy for error responses that do not come from the SDK

    Augment responses to better identify when error responses do not come the SDK but rather intermediary proxies or app timeouts.

  • #4571 fix: Display errored attempts without step as Function Error rather than Finalization

    Errored attempts that never resolved to a step are displayed as "Function error" rather than "Finalization" in the trace view. …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Inngest

Version 1.36.0: AI-Metadata-Felder umbenannt, Insights-Abfragen anpassen

Inngest 1.36.0 benennt die AI-Metadata-Felder .model in .request_model und .system in .provider um, unterscheidet zwischen Request- und Response-Modell und schließt Go-Sicherheitslücken, sodass Insights-Abfragen angepasst werden müssen.

Release Notes

  • #4516 fix: Update AI Metadata field names

    For AI Metadata extracted from extended traces, step.ai.wrap, and step.ai.infer, the .model field has been renamed to .request_model and .system has been renamed .provider to better match the OpenTelemetry GenAI standards.

  • #4518 feat: Differentiate between request and response model for AI Metadata extraction with ai.step.*

    • AI Metadata extracted with ai.step.wrap or ai.step.infer will now differentiate between request and response models

Migration Notes

  • #4516 fix: Update AI Metadata field names

    Insights queries that use AI Metadata fields of .model and .system should be updated to use .request_model and .provider, respectively.

Changelog

🚀 Features

  • Differentiate between request and response model for AI Metadata extraction with ai.step.* (#4518)

🐛 Bug Fixes

  • (release) Open homebrew-tap PRs as ready for review (non-draft) (#4576)
  • Update AI Metadata field names (#4516)

⚙️ Miscellaneous Tasks

  • (go) Move one unit test job to Depot (#4568)

🛡️ Security

  • Address Go vulnerabilities (#4570)

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Inngest

Version 1.35.0: Experiments und Sessions in REST API v2 und CLI

Inngest 1.35.0 fügt der REST API v2 und der CLI Endpunkte für Experiments und Sessions hinzu, visualisiert numerische Experiment-Metriken als Boxplots und zeigt die Key-Queues-Einstellung in der Funktionsansicht an.

Release Notes

  • #4504 feat(api): experiments api

    Adds experiment endpoints to REST V2 API and CLI: GET /v2/experiments GET /v2/apps/{app_id}/functions/{function_id}/experiments GET /v2/apps/{app_id}/functions/{function_id}/experiments/{experiment_id}

    Adds sessions endpoints to REST V2 API and CLI: GET /v2/sessions GET /v2/sessions/{session_key} GET /v2/sessions/{session_key}/{session_id}/runs

Changelog

🚀 Features

  • (experiments) Visualize numeric metrics using box plots (#4517)
  • (function-view) Show key queues setting (#4546)
  • (experiments) Update charts/layout to match new design (#4551)
  • (queue) Jitter PartitionRequeue default case (#4561)
  • (api) Experiments api (#4504)

🐛 Bug Fixes

  • Should not coalesce parallel steps for the V1 execution engine (#4538)
  • (experiments) Fix boxplot colors (#4542)

🚜 Refactor

  • (queue) Clean up QueueManager interface (#4541)

⚙️ Miscellaneous Tasks

  • (go) Drop key-queues test matrix dimension (#4552)
  • Upload test results to CodeCov to analyze flake rates (#4545)
  • Use a depot runner for linting (#4554)
  • (queue) Add timeout to backlog size (#4556)
  • Track partition processing that yielded 0 peeks (#4562)
  • Cleanup unused queue injections (#4564)

◀️ Revert

  • Always SavePending after parallel ops to coalesce discovery (#4021) (#4534)

Originalquelle(öffnet in neuem Tab)Problem melden