chore(release): v0.8.0#256
Open
GrowthX-Team wants to merge 1 commit into
Open
Conversation
0cd791a to
10cfaa6
Compare
10cfaa6 to
2a45de4
Compare
2a45de4 to
f2eda4c
Compare
f2eda4c to
381260a
Compare
381260a to
a2a565f
Compare
a2a565f to
6fb9bd7
Compare
6fb9bd7 to
07425f9
Compare
07425f9 to
08b8287
Compare
08b8287 to
adc85d4
Compare
adc85d4 to
958138a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@outputai/cli@0.8.0
Minor Changes
aggregations.Patch Changes
d67ad85: Faster CLI startup: ship
oclif.manifest.jsonin the published package so only the invoked command module is loaded (instead of importing every command on every invocation), move the update check off the critical path (the init hook now only reads the local cache and refreshes it via a detached background process with a 5s registry timeout, instead of awaiting an unboundednpm viewsubprocess), and loadundicionly when a proxy env var is configured.bd6bd49:
workflow costnow calculates costs from the trace events themselves (the as-charged "Original" cost) and appliescosts.ymlas an override layer (the "Adjusted" cost), displaying both per model and per host. This fixes models with nocosts.ymlentry (e.g.gpt-5.5) and HTTP hosts (e.g.api.exa.ai,api.firecrawl.dev) previously reporting $0, and surfaces where the configuredcosts.ymlrate diverges from what was actually charged. The bottom line shows the adjusted total with the as-charged total alongside.Costs come exclusively from trace cost attributes: LLM nodes with an
llm:usageevent and HTTP calls with anhttp:request:costevent are counted as-charged (even on error responses — the event proves a charge); calls without events are not priced. Traces from SDK versions that predate cost attributes (< 0.5) report no costs. Only exact (computed) recomputes override an event cost — estimates and failed recomputes never do, and a configured$0price is now honored. Body-dependentcosts.ymlservice rules require traces recorded withOUTPUT_TRACE_HTTP_VERBOSE=true(the dev default).--format jsonfield changes (the report shape changed; update any scripts parsing it):llmTotalCost→llmOriginalCost/llmAdjustedCost;services[]/serviceTotalCost→httpCosts[](grouped byhost) withhttpOriginalCost/httpAdjustedCost;unknownModelsremoved; per-callcost/warning→originalCost/adjustedCost; neworiginalTotalCost;totalCostis now the adjusted total.de30052: Surface workflow aliases and honor
OUTPUT_CATALOG_IDinoutput workflow list.(aliases: ...)to workflows that have registered aliases, which previously only appeared in--format table/--format json(OUT-444).--catalogflag (envOUTPUT_CATALOG_ID) that resolves workflows from a specific catalog, falling back to the server-default catalog — matching the existing behavior ofrunandstart(OUT-489).Updated dependencies [ae5bab4]
@outputai/core@0.8.0
Minor Changes
@outputai/core; workflows no longer collect activity attributes into finalaggregationstotals or expose those totals in workflow run results.WorkflowInvocationConfigurationtoWorkflowInvocationOptions.activityOptionsinstead of the previousoptionsproperty.Patch Changes
ad03627: improve worker startup time by only calculating workflow sources
306c136: Fixed missing eventDate fields on hook types.
c005dac: Add an opt-in
output-worker --checkworkflow bundle check that reproduces the worker's webpack bundling without a Temporal server, catching bad workflow imports — e.g. a transitivenode:built-in — before they crash-loop the worker at startup.tsccannot detect these; only the Temporal bundle can.output-worker --checkbundles workflows via the samebundleWorkflowCodepathWorker.createuses, exits non-zero with the offending module named, and needs no Temporal connection or worker env.output:worker:checkscript plus README/CI guidance (not wired into any build).@outputai/llm@0.8.0
Minor Changes
ae5bab4: Add per-message provider options to
.promptfiles viamessageOptions.messageOptionssets in front matter and attach them to message blocks withoptions="<name>"(e.g.<system options="cached">); each set is a provider-namespacedproviderOptionsobject merged onto that message.{ anthropic: { cacheControl: { type: ephemeral } } }) and any other per-message provider option, on any provider.input_cached) even for models whose pricing record lacks acache_readrate, so cache savings are visible in usage aggregations instead of silently disappearing.Patch Changes
@outputai/credentials@0.8.0
Patch Changes
@outputai/evals@0.8.0
Patch Changes
@outputai/output@0.8.0
Patch Changes
@outputai/http@0.8.0
Patch Changes
output-api@0.8.0
Minor Changes
aggregations.Patch Changes
d67ad85:
getWorkflowResultnow fetches only the first history event (WorkflowExecutionStarted) to extract the workflow input, instead of paging through the full event history. Makes input extraction on the result endpoints (/workflow/:id/resultand/workflow/:id/runs/:rid/result) O(1) regardless of history size.2a4105c: Expose structured workflow failure details (
failureobject withmessage,type,retryable, and a sanitizedcausechain) in/workflow/runand/workflow/:id/resultresponses, alongside the existingerrorstring. Also log Temporal/gRPC client errors with full nested context (cause chain, gRPCcode/details, redacted metadata keys,workflowId/runId/taskQueue/query) while keeping client-facing HTTP responses sanitized.db8ddd7: The
continuedworkflow status was renamed tocontinued_as_newin API responses.Explicit Status Fields
POST /workflow/runstatusresponse.data.statusGET /workflow/{id}/resultstatusresponse.data.statusGET /workflow/{id}/runs/{rid}/resultstatusresponse.data.statusGET /workflow/{id}/statusstatusresponse.data.statusGET /workflow/{id}/runs/{rid}/statusstatusresponse.data.statusGET /workflow/runsruns[].statusresponse.data.runs[].statusHistory Metadata Status Fields
These endpoints also return workflow status in the history metadata object. The OpenAPI schema currently leaves this nested object unexpanded.
GET /workflow/{id}/historyworkflow.statusresponse.data.workflow.statusGET /workflow/{id}/runs/{rid}/historyworkflow.statusresponse.data.workflow.statusBackwards support
In the CLI, the old value is still supported.