Every QR Code v0.1.2 makes saved 3D QR worlds reproducible across future generator upgrades.
What is new
- React now accepts generatorVersion={1}.
- The Web Component now accepts generator-version="1".
- The core, seed model, Tree/Terrain geometry, and shaders use explicit version registries.
- Golden fingerprints protect released v1 output from accidental visual changes.
- Unsupported recorded versions fail clearly instead of silently using a different recipe.
- Package descriptions and keywords now better describe the React QR generator, Web Component, and WebGPU renderer.
The simple v1 / v2 rule
A generator version is a drawing recipe, not an npm version.
- A saved v1 world keeps using the v1 recipe.
- A future v2 world will use a separate v2 recipe.
- A newer npm package can contain both recipes.
- Updating the package does not rewrite a saved v1 world.
v0.1.2 ships the versioning contract and the frozen v1 recipe. It does not introduce a v2 visual recipe yet.
Upgrade
pnpm update @every-qrcode/react@0.1.2
# or
pnpm update @every-qrcode/web-component@0.1.2
For saved or shared worlds, store CURRENT_GENERATOR_VERSION next to the URL and pass the recorded value back when rendering. Existing records without a version should be migrated once to version 1.
Community models
The contribution guide now breaks model work into smaller slices. Public proposals are open for Hokusai Waves, Crystalline, and Mechanical. Visual references, geometry prototypes, WGSL experiments, tests, and documentation are all welcome.