max / makeover-webview

Bump to 0.59.2, because 0.59.1 is published and this tree is not it 7f2ba78 changed the emitted stylesheet banner while the manifest still said 0.59.1, which is on crates.io. That makes one version number name two different crates, which is the silent staleness problem 87a7a4d1 exists to kill. No consumer needs a forward fix: makeover-build pins makeover-webview = "0.59.1" from crates.io rather than by path, so it keeps resolving the published crate until this is released.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: Max Johnson <me@maxj.phd> · 2026-08-23 21:59 UTC

Signed with PGP, not checked

Commit: 07d0acbacbbb212bd24594c88ee67fefa7ff96a8

Parent: 7f2ba78

1 file changed, +1 insertion, -1 deletion

M Cargo.toml +1 -1

			@@ -1,6 +1,6 @@
1	1		[package]
2	2		name = "makeover-webview"
3		-	version = "0.59.1"
	3	+	version = "0.59.2"
4	4		edition = "2024"
5	5		# One copy of this renderer per dependency graph, enforced by cargo rather than
6	6		# by remembering. Two versions means the generated stylesheet and the emitted