Skip to content

chore: update versions (beta)#776

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

chore: update versions (beta)#776
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented May 30, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm 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.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@effect-app/infra@4.0.0-beta.291

Patch Changes

  • 848d26d: Capture more of the rpc request payload in the rpc.request.payload span
    attribute.

    The summarizer was one level deep: top-level scalars were kept, but any nested
    object collapsed to Object[N] and any array to Array[N], hiding useful
    inputs (carrier, packageType, dimensions, ids, per-item amounts, …).

    It now recurses into nested objects up to PAYLOAD_MAX_DEPTH (4) and samples
    arrays to their first PAYLOAD_ARRAY_HEAD (20) elements, appending a …N more
    marker when longer — so item arrays stay diagnosable without dumping the whole
    tail on high-frequency commands. Long strings are still snipped at 256 chars,
    and password/secret/token keys are redacted at any depth (previously only
    a top-level password).

    • effect-app@4.0.0-beta.291

@effect-app/vue@4.0.0-beta.291

Patch Changes

  • fa3533e: Keep the previous suspense value across reactive-arg atom switches.

    A reactive arg re-points a resolved suspense query at a different family atom; the fresh atom starts Initial (no previousSuccess carried over), so the always-defined data computed found undefined and threw Internal Error: suspense resolved without a latest value during the next render flush. The always-defined ref now serves the last defined value across that transition (TanStack's keepPreviousData — Vue cannot re-suspend after mount); waiting/failure of the new fetch stays observable on the result ref. Applied to .suspense(), .suspenseNew() and useAtomSuspense via a shared latestDefined helper. It only throws when there has never been a value, which is unreachable once the suspense await resolved.

    • effect-app@4.0.0-beta.291

@effect-app/vue-components@4.0.0-beta.291

Patch Changes

  • Updated dependencies [fa3533e]
    • @effect-app/vue@4.0.0-beta.291
    • effect-app@4.0.0-beta.291

effect-app@4.0.0-beta.291

@effect-app/e2e@4.0.0-beta.291

Patch Changes

  • Updated dependencies [848d26d]
  • Updated dependencies [fa3533e]
    • @effect-app/infra@4.0.0-beta.291
    • @effect-app/vue@4.0.0-beta.291
    • effect-app@4.0.0-beta.291

@github-actions github-actions Bot force-pushed the changeset-release/main branch 8 times, most recently from 861b7ed to efa7347 Compare June 1, 2026 15:56
@github-actions github-actions Bot force-pushed the changeset-release/main branch 15 times, most recently from 5871083 to 5a7270d Compare June 21, 2026 08:53
@github-actions github-actions Bot force-pushed the changeset-release/main branch 7 times, most recently from 2dd101f to d1cb6f0 Compare June 24, 2026 07:26
@github-actions github-actions Bot force-pushed the changeset-release/main branch 3 times, most recently from 75c57ec to 91090ab Compare June 29, 2026 18:35
@github-actions github-actions Bot force-pushed the changeset-release/main branch from 91090ab to 1d781e1 Compare July 1, 2026 12:27
@github-actions github-actions Bot force-pushed the changeset-release/main branch from 1d781e1 to 4f89682 Compare July 2, 2026 05:58
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.

0 participants