chore: release packages

[github-actions]

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.

Releases

@pkishorez/devtools@0.0.2

Patch Changes

• Updated dependencies [4be44ed]:
  • @pkishorez/lotel@0.0.2
  • laymos@0.0.2
  • std-toolkit@0.0.2

laymos@0.0.2

Patch Changes

• 4be44ed Thanks @pkishorez! - Move the Effect trace recorder into its own package, @pkishorez/effect-trace-recorder.

  Breaking: the @pkishorez/lotel/trace subpath export has been removed. Import
  makeTraceRecorder and the Captured* types from @pkishorez/effect-trace-recorder
  instead:

  -import { makeTraceRecorder } from '@pkishorez/lotel/trace';
  +import { makeTraceRecorder } from '@pkishorez/effect-trace-recorder';

  The recorder never used anything from lotel's server, and lotel never used the
  recorder — pulling it out lets consumers capture Effect spans without depending on
  the OTLP server, and drops laymos' dependency on @pkishorez/lotel entirely.
  This removes the std-toolkit -> laymos -> lotel -> std-toolkit workspace cycle
  that made build ordering non-deterministic.

• Updated dependencies [4be44ed]:

  • @pkishorez/effect-trace-recorder@0.0.2

@pkishorez/lotel@0.0.2

Patch Changes

• 4be44ed Thanks @pkishorez! - Move the Effect trace recorder into its own package, @pkishorez/effect-trace-recorder.

  Breaking: the @pkishorez/lotel/trace subpath export has been removed. Import
  makeTraceRecorder and the Captured* types from @pkishorez/effect-trace-recorder
  instead:

  -import { makeTraceRecorder } from '@pkishorez/lotel/trace';
  +import { makeTraceRecorder } from '@pkishorez/effect-trace-recorder';

  The recorder never used anything from lotel's server, and lotel never used the
  recorder — pulling it out lets consumers capture Effect spans without depending on
  the OTLP server, and drops laymos' dependency on @pkishorez/lotel entirely.
  This removes the std-toolkit -> laymos -> lotel -> std-toolkit workspace cycle
  that made build ordering non-deterministic.

• Updated dependencies []:

  • std-toolkit@0.0.2

@pkishorez/effect-trace-recorder@0.0.2

Patch Changes

• 4be44ed Thanks @pkishorez! - Move the Effect trace recorder into its own package, @pkishorez/effect-trace-recorder.

  Breaking: the @pkishorez/lotel/trace subpath export has been removed. Import
  makeTraceRecorder and the Captured* types from @pkishorez/effect-trace-recorder
  instead:

  -import { makeTraceRecorder } from '@pkishorez/lotel/trace';
  +import { makeTraceRecorder } from '@pkishorez/effect-trace-recorder';

  The recorder never used anything from lotel's server, and lotel never used the
  recorder — pulling it out lets consumers capture Effect spans without depending on
  the OTLP server, and drops laymos' dependency on @pkishorez/lotel entirely.
  This removes the std-toolkit -> laymos -> lotel -> std-toolkit workspace cycle
  that made build ordering non-deterministic.