Skip to content

Support vize 0.16 and prepare 0.19.4 - #48

Merged
dannote merged 2 commits into
masterfrom
vize-0.16
Oct 3, 2026
Merged

dannote merged 2 commits into
masterfrom
vize-0.16

Conversation

@dannote

@dannote dannote commented Oct 3, 2026 •

Copy link
Copy Markdown
Member

Volt requires vize ~> 0.15.0, so it can't be installed alongside vize 0.16.0, which was released on October 1. PhoenixVapor needs vize 0.16 and Volt together. This requires ~> 0.16.0, moves the lock to 0.16.0, and prepares the 0.19.4 release: the version bump and a dated CHANGELOG section.

Why this is safe

vize 0.16's only breaking change is to Vize.vapor_split/1, which Volt doesn't call. Events and v-model are now returned as bindings instead of phx-* attributes; see elixir-volt/vize_ex#6.

The vize functions Volt uses keep their public API:

  • Vize.compile_sfc
  • Vize.parse_sfc
  • Vize.SFC.collect_template_assets
  • Vize.CSS: compile, compile_sass, select, rewrite_urls, parse_ast, print_ast, postwalk

Internally, vize's NIFs now take typed options maps, and SFC block locations gain tag_start/tag_end.

Volt follows vize's latest minor, as 0.19.0 did with 0.15, rather than supporting two pre-1.0 minors.

Verification

MIX_ENV=test mix test on vize 0.16.0, excluding the browser-tagged tests: 728 passed, 5 skipped. mix format --check-formatted and mix compile --warnings-as-errors pass.

Volt required vize ~> 0.15.0, so it couldn't be installed alongside
vize 0.16, which PhoenixVapor needs. Accept 0.15 or 0.16. vize 0.16
changes only Vize.vapor_split/1, which Volt doesn't call; the
functions Volt uses (compile_sfc, parse_sfc, SFC template assets and
Vize.CSS) are unchanged. The lock moves to 0.16.0, and the suite passes
on it.
Pre-1.0 vize minors may break, so supporting 0.15 as well would mean
testing both. Volt follows vize's latest minor, as 0.19.0 did with 0.15.
@dannote
dannote merged commit 9347ba3 into master Oct 3, 2026
2 checks passed
@dannote
dannote deleted the vize-0.16 branch October 3, 2026 08:27
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.

1 participant