Skip to content
This repository was archived by the owner on Oct 2, 2026. It is now read-only.

Release v0.5.6 - #46

Merged
lchoquel merged 3 commits into
mainfrom
release/v0.5.6
Sep 27, 2026
Merged

lchoquel merged 3 commits into
mainfrom
release/v0.5.6

Conversation

@lchoquel

@lchoquel lchoquel commented Sep 27, 2026 •

Copy link
Copy Markdown
Member

Release v0.5.6

Bumps version from 0.5.5 to 0.5.6. Promotes dev → main.

Changelog

Changed

  • The web app template runs on @pipelex/sdk 0.26.0: the SDK's RunFailedError now carries a failed run's stored error report and its ApiResponseError a refused request's problem document, which the template's failure display reads. A project made from an earlier template keeps its own SDK range, and moving it onto 0.26.0 is a minor step whose breaking changes the SDK's changelog lists.

Fixed

  • A failed durable run says why: the web app template's failure display now reads a failed run's stored error report and shows the runtime's reason with the failing pipe, its advice as the next step, whether running it again can help, and a line to quote to support with the run id, the error type and when the run ended, where it used to show only "Run finished with status FAILED; no result available". A model provider's raw error text is kept out of everything the person can read, and a run that ended with no stored report keeps the old sentence.
  • A refused run says what to do: when the runner refuses to run a method, at the start of a durable run or on a blocking run, the web app template's failure display now shows the runtime's next step in place of a generic hint, says whether running it again can help when the runtime says so, and lists the method's validation items under the technical details, with an unknown model's reference and the model deck's suggestions. An answer that carries none of this keeps its old wording.

Closes L-260927-a70072

🤖 Generated with Claude Code


Summary by cubic

Releases v0.5.6, bumping the web app template's @pipelex/sdk to 0.26.0 and making the failure display explain why a run failed or was refused.

Bug Fixes

  • A failed durable run now shows the runtime's reason, next step, retry verdict, and a support line, instead of only "Run finished with status FAILED; no result available".
  • A refused run now shows the runtime's next step and the method's validation items.
  • The model provider's raw error text never reaches the person reading the display.
  • Runs with no stored report keep the old wording.

Dependencies

  • The template moves from @pipelex/sdk 0.25.1 to 0.26.0.

Written for commit a363d4c. Summary will update on new commits.

Review in cubic

lchoquel and others added 3 commits September 27, 2026 12:50
A failed durable run in the web app template now shows why it failed,
read from the run's stored error report rather than the fixed "no result
available" sentence: the runtime's title and message with the model
provider's raw text cut out, the user action's detail as the next step,
a retry line only when the report gives a retryable verdict, and a
support line with the run id, the error type and when the run ended. A
run with no stored report keeps today's wording, and docs/errors.md plus
the template's CLAUDE.md describe where the reason comes from. The
`@pipelex/sdk` git pin is the sprint's and collapses onto the published
release before merge.

Closes L-260925-b0e3ca

🤖 Generated with [Claude Code](https://claude.com/claude-code)

<!-- This is an auto-generated description by cubic. -->
---
## Summary by cubic
A failed durable run in the web-app template now explains why it failed,
reading the run's stored error report instead of always showing "no
result available": the runtime's title and message, the user action's
detail as the next step, a retry line only when the report gives a
retryable verdict, and a support line with the run id, error type, and
when the run ended. Runs with no stored report keep the old wording.

**Bug Fixes**
- Pulls the report from the result lookup, falling back to the status
read, and passes the run's `finished_at` for the support line.
- Strips the model provider's raw error text from everything a person
can read, including the technical details.
- Drops `wait_and_retry` advice from a failed run, since nothing retries
it after it ends.
- Adds `docs/errors.md` and updates the template's `CLAUDE.md` to
describe where the reason comes from.

**Dependencies**
- Bumps `@pipelex/sdk` to `^0.26.0`, collapsing the sprint's git pin
onto the published release.

Closes L-260925-b0e3ca

<sup>Written for commit 51f0b3b.
Summary will update on new commits.</sup>

<a
href="https://cubic.dev/pr/Pipelex/pipelex-method-apps/pull/44?utm_source=github"
target="_blank" rel="noopener noreferrer"
data-no-image-dialog="true"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source
media="(prefers-color-scheme: light)"
srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img
alt="Review in cubic"
src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a>

<!-- End of auto-generated description by cubic. -->

---------

Co-authored-by: Claude Opus 5.5 <[email protected]>
A run the runner refuses, at /v1/start in durable mode or /v1/execute in
blocking mode, is now classified from its problem document instead of by
HTTP status alone. The hint is the runtime's user action (except a stale
wait_and_retry promise or the unknown-kind fallback), a retry line
appears only when `retryable` says so, and the method's validation items
go in the technical details with an unknown model's reference and the
deck's suggestions. An answer with no problem document keeps today's
wording. This PR is stacked on pipelex-method-apps#44 and shares its
next-step and retry helpers with the failed-run classification.

Closes L-260926-b72417

🤖 Generated with [Claude Code](https://claude.com/claude-code)

<!-- This is an auto-generated description by cubic. -->
---
## Summary by cubic
A run the runner refuses — at `/v1/start` in durable mode or
`/v1/execute` in blocking mode — is now classified from its problem
document instead of by HTTP status alone. The runtime's
`user_action.detail` becomes the hint (except `wait_and_retry` and
`unknown` kinds), a retry line appears only when `retryable` says so,
and the method's validation items — with an unknown model's reference
and the model deck's suggestions — are listed ahead of the raw body in
technical details. An answer with no problem document keeps today's
wording, and the next-step and retry helpers are shared with the
failed-run classification.

Closes L-260926-b72417.

<sup>Written for commit 0de7e93.
Summary will update on new commits.</sup>

<a
href="https://cubic.dev/pr/Pipelex/pipelex-method-apps/pull/45?utm_source=github"
target="_blank" rel="noopener noreferrer"
data-no-image-dialog="true"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source
media="(prefers-color-scheme: light)"
srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img
alt="Review in cubic"
src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a>

<!-- End of auto-generated description by cubic. -->

---------

Co-authored-by: Claude Opus 5.5 <[email protected]>
Co-Authored-By: Claude Opus 5.5 <[email protected]>
@lchoquel
lchoquel merged commit 342b1cb into main Sep 27, 2026
3 checks passed
@lchoquel
lchoquel deleted the release/v0.5.6 branch September 27, 2026 11:09
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant