Skip to content

chore: version packages - #132

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

chore: version packages#132
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 20, 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.

Releases

@camp-dev/shaders@0.19.0

Minor Changes

  • 0b58731: The three packages are renamed. @lovo/matter is now @camp-dev/shaders, @lovo/matter-react is now @camp-dev/shaders-react, and @lovo/matter-cli is now @camp-dev/shaders-cli. The repository moved to github.com/campdotdev/shaders. Update your dependency names and every import specifier. Apart from the removals below, the exports themselves are unchanged.

    The CLI binary is renamed from matter-cli to shaders-cli, and its config file from matter.config.json to shaders.config.json. Rename the file and update any script that calls the old binary. Two defaults that shaders-cli init writes also change: componentsDir goes from src/components/matter to src/components/shaders, and registryUrl now points at campdotdev/shaders instead of lovo-hq/matter. A config you already have keeps the values it records, so edit its registryUrl by hand or re-run init with --force.

    MatterError and MatterErrorCode in @camp-dev/shaders-react are now ShadersError and ShadersErrorCode. A catch block that tests instanceof MatterError has to switch to the new name.

    The READMEs drop their migration notes for the Matter* aliases that 0.4.0 deprecated, such as MatterScene and MatterScheduler. The aliases themselves left the source several releases ago.

  • fc0d728: Seeded randomness now renders the same pattern on the WebGPU and WebGL2 backends. three's TSL hash() writes its PCG constants as float literals, which GLSL rounds to a different hash than WGSL computes, so the same seed produced a different Voronoi layout in Safari than in Chrome. The new stableHash and stableHashUint exports run the same PCG with integer-typed constants and chain hash streams u32 to u32, and voronoiCells, grain, metaballs, and ditherPattern now draw from them.

    This costs one visual break. Deriving seeds from the raw hash word re-rolls every seeded layout once, on both backends, so any seed value renders a new pattern after this release. The new pattern is stable from here.

Versions 0.18.0 and below shipped as @lovo/matter before the project moved to the camp-dev org. Releases 1.0.0 through 3.9.0 from that history are renumbered here as 0.7.0 through 0.18.0.

@camp-dev/shaders-cli@0.19.0

Minor Changes

  • 0b58731: The three packages are renamed. @lovo/matter is now @camp-dev/shaders, @lovo/matter-react is now @camp-dev/shaders-react, and @lovo/matter-cli is now @camp-dev/shaders-cli. The repository moved to github.com/campdotdev/shaders. Update your dependency names and every import specifier. Apart from the removals below, the exports themselves are unchanged.

    The CLI binary is renamed from matter-cli to shaders-cli, and its config file from matter.config.json to shaders.config.json. Rename the file and update any script that calls the old binary. Two defaults that shaders-cli init writes also change: componentsDir goes from src/components/matter to src/components/shaders, and registryUrl now points at campdotdev/shaders instead of lovo-hq/matter. A config you already have keeps the values it records, so edit its registryUrl by hand or re-run init with --force.

    MatterError and MatterErrorCode in @camp-dev/shaders-react are now ShadersError and ShadersErrorCode. A catch block that tests instanceof MatterError has to switch to the new name.

    The READMEs drop their migration notes for the Matter* aliases that 0.4.0 deprecated, such as MatterScene and MatterScheduler. The aliases themselves left the source several releases ago.

Versions 0.18.0 and below shipped as @lovo/matter-cli before the project moved to the camp-dev org. Releases 1.0.0 through 3.9.0 from that history are renumbered here as 0.7.0 through 0.18.0.

@camp-dev/shaders-react@0.19.0

Minor Changes

  • 0b58731: The three packages are renamed. @lovo/matter is now @camp-dev/shaders, @lovo/matter-react is now @camp-dev/shaders-react, and @lovo/matter-cli is now @camp-dev/shaders-cli. The repository moved to github.com/campdotdev/shaders. Update your dependency names and every import specifier. Apart from the removals below, the exports themselves are unchanged.

    The CLI binary is renamed from matter-cli to shaders-cli, and its config file from matter.config.json to shaders.config.json. Rename the file and update any script that calls the old binary. Two defaults that shaders-cli init writes also change: componentsDir goes from src/components/matter to src/components/shaders, and registryUrl now points at campdotdev/shaders instead of lovo-hq/matter. A config you already have keeps the values it records, so edit its registryUrl by hand or re-run init with --force.

    MatterError and MatterErrorCode in @camp-dev/shaders-react are now ShadersError and ShadersErrorCode. A catch block that tests instanceof MatterError has to switch to the new name.

    The READMEs drop their migration notes for the Matter* aliases that 0.4.0 deprecated, such as MatterScene and MatterScheduler. The aliases themselves left the source several releases ago.

Versions 0.18.0 and below shipped as @lovo/matter-react before the project moved to the camp-dev org. Releases 1.0.0 through 3.9.0 from that history are renumbered here as 0.7.0 through 0.18.0.

@shaders/editor@0.0.1

Patch Changes

  • Updated dependencies [0b58731]
  • Updated dependencies [fc0d728]
    • @camp-dev/shaders@0.19.0
    • @camp-dev/shaders-react@0.19.0

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 2 times, most recently from 0a772d4 to 7b4b4b1 Compare August 21, 2026 02:31
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 7b4b4b1 to 4560bca Compare August 21, 2026 13:51
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