fix(ci): ask pantry for a bun range it can actually satisfy

deps.yamlmodified+9-1

Changes to deps.yaml

		⋯13 linesShow the 13 lines above this hunk@@ -14,8 +14,16 @@
14	14	# mysql and postgres are still skipped as unsupported, so their spec is inert
15	15	# today — they are ranges so that being added upstream is a no-op, not an
16	16	# outage.
	17	+#
	18	+# Keep every range satisfiable by the pantry registry, not just well-formed.
	19	+# `bun: ^1.3.14` was well-formed and unsatisfiable: pantry's newest bun.sh is
	20	+# 1.3.11, so the range matched nothing and the install failed outright. It only
	21	+# surfaced intermittently because the action evaluates this spec on its
	22	+# reconcile path and skips it when it takes the `latest` shortcut.
	23	+#
	24	+# `^1.3.11` picks up 1.3.14 on its own once pantry publishes it.
17	25	dependencies:
18		- bun: ^1.3.14
	26	+ bun: ^1.3.11
19	27	mysql: ^8.0.45
20	28	postgres: ^18.0.0
21	29	sqlite: ^3.52.0