Release v0.7.0 · linebender/bevy_vello

0.7.0 - 2025-02-27

This release supports Bevy version 0.15 and has an MSRV of 1.85.

Added VelloView marker component used for identifying cameras rendering vello content.
Added VelloEntityCountDiagnosticsPlugin which can be used to provide vello entity type data at runtime. See the diagnostics example.
Added VelloFrameProfileDiagnosticsPlugin which can be used to provide vello frame profile data at runtime. See the diagnostics example.

bevy_vello now uses Bevy 0.15
Camera2d now requires a VelloView marker for rendering.
VelloAsset assets have been separated into VelloSvg and VelloLottie
VelloAssetBundle has been separated into VelloSvgBundle and VelloLottieBundle
Handle<VelloAsset> has been separated into VelloSvgHandle and VelloLottieHandle
VelloAssetAnchor has been separated into VelloSvgAnchor and VelloLottieAnchor
The license on bevy_vello no longer includes OFL 1.1
The experimental-dotLottie feature was removed and merged into the lottie feature.
DotLottiePlayer was renamed to LottiePlayer.
All render types (VelloSvgHandle, VelloLottieHandle, VelloScene, and VelloTextSection) now have required components as an alternative to their bundle counterparts.

Removed DebugVisualizations. Now you should use BorderColor for UI Nodes and Gizmos for world assets. Several examples show this capability, such as the svg and svg_ui examples.
Removed CoordinateSpace. If you wish to render scene or asset UI, insert a Node component. For more information, see the scene_ui, svg_ui, or lottie_ui examples.
VelloText (with CoordinateSpace::ScreenSpace) can no longer render text in screen space. You should be using bevy's native Text for UI text, which is more feature rich and widely used.

We no longer bundle the default font twice when the default_font feature is active.

Full Changelog: v0.6.1...v0.7.0