What changed
Symfony released Reprise 1.0.0 on August 26, 2026. The project remains a thin Symfony integration layer around Vite and Rsbuild rather than a bundler itself, but the experimental notice is now gone. Symfony says Reprise’s public API follows semantic versioning and Symfony’s backward-compatibility promise: changes within a major version should be deprecated before removal rather than appearing as arbitrary 0.x breakage. The earlier 0.8 release had already restored an Encore-compatible stable copied-file path option for migrations.
Why it matters
The main blocker in BTN’s earlier dossier was not feature coverage alone; it was adoption risk. Symfony was explicitly steering new bundler work away from low-maintenance Webpack Encore while Reprise itself was still experimental. Version 1.0 closes that gap. Teams can now plan migration around a stable API contract, making Reprise a much more credible default for new Symfony projects and for Encore migrations that need Vite or Rsbuild without accepting pre-1.0 churn.
The recommendation now has a stability contract
Symfony’s Encore documentation already marks Webpack Encore as a low-maintenance legacy path and recommends Reprise for modern bundler integration. Reprise 1.0 makes that recommendation operationally easier to follow by removing the experimental warning and committing the public API to semantic versioning and Symfony’s backward-compatibility policy.
Reprise still leaves bundling to Vite or Rsbuild
The architecture has not changed: Vite or Rsbuild performs bundling, hashing, source maps, HMR and dev-server work, while Reprise supplies Symfony-specific entrypoint/manifest integration, Twig tags and framework glue. The narrow scope is part of why Symfony says it was able to stabilize the API quickly.
The migration work still needs production validation
Version 1.0 reduces API-change risk but does not make an Encore migration zero-effort. Teams should still compare manifests, copied assets, Twig helpers, Symfony UX/Stimulus behavior, CDN paths and deployment caching. Reprise 0.8’s stable-path copy option remains particularly relevant to codebases that depend on fixed asset locations.