Skip to content

chore(deps): bump @styx-api/core to 0.6.0 - #13

Merged
nx10 merged 1 commit into
mainfrom
chore/bump-styx-core-0.6.0
Jun 30, 2026
Merged

chore(deps): bump @styx-api/core to 0.6.0#13
nx10 merged 1 commit into
mainfrom
chore/bump-styx-core-0.6.0

Conversation

@nx10

@nx10 nx10 commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

Bumps @styx-api/core 0.5.0 -> 0.6.0 (styx-ts#48, published to npm).

Effect

The Python results tab now renders nested structs / union variants as factory calls - e.g. ants.tool_corrected_output_params(corrected_output_file_name="...") - instead of raw tagged dicts {"@type": ...}. Root kwargs with camelCase wire ids also become snake_case. TypeScript snippets are unchanged.

No hub code changes

The snippet flows straight from renderPythonCall in @styx-api/core (worker.ts) with zero hub-side snippet logic, so only the pin + lockfile move. The build-time __STYX_CORE_VERSION__ lockstep check resolves to the new version on rebuild.

Validated locally

npm ci (clean, no lock churn), npm run check (0 errors), npm run test (206 pass), npm run build (success) - all against the pinned 0.6.0.

Picks up nested-struct `_params` factories and snake_case kwargs in the
generated Python snippets (styx-ts#48). Python results tab now renders
nested structs / union variants as factory calls
(`tool_x_params(...)`) instead of raw tagged dicts; TypeScript snippets
are unchanged. No hub code changes needed - the snippet flows straight
from `renderPythonCall` in @styx-api/core.
@nx10
nx10 merged commit 6eb0485 into main Jun 30, 2026
4 checks passed
@nx10
nx10 deleted the chore/bump-styx-core-0.6.0 branch June 30, 2026 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant