@omit-design/preset-mobile 0.5.0

[preset-mobile 0.4.0 + cli 0.4.2] - 2026-05-11 — Peer dep follow-up

Fixed

• preset-mobile bumped 0.3.0 → 0.4.0 so its peerDependencies.@omit-design/engine
  range (^0.4.0) reaches npm. The 0.4.0 release PR (#8) updated the peer
  locally but didn't republish preset-mobile, leaving npx omit-design init
  failing with ERESOLVE because the published preset-mobile@0.3.0 still
  declared engine ^0.3.0. Republishing under 0.4.0 (no source change other
  than the peer range — breaking by SemVer) fixes the install chain.
• scaffold template pin @omit-design/preset-mobile ^0.3 → ^0.4 (in
  templates/init/package.json.tmpl).
• cli 0.4.1 → 0.4.2 carrying the template-pin change. No source change
  to CLI commands.

@omit-design/engine 0.5.0

[preset-mobile 0.4.0 + cli 0.4.2] - 2026-05-11 — Peer dep follow-up

Fixed

• preset-mobile bumped 0.3.0 → 0.4.0 so its peerDependencies.@omit-design/engine
  range (^0.4.0) reaches npm. The 0.4.0 release PR (#8) updated the peer
  locally but didn't republish preset-mobile, leaving npx omit-design init
  failing with ERESOLVE because the published preset-mobile@0.3.0 still
  declared engine ^0.3.0. Republishing under 0.4.0 (no source change other
  than the peer range — breaking by SemVer) fixes the install chain.
• scaffold template pin @omit-design/preset-mobile ^0.3 → ^0.4 (in
  templates/init/package.json.tmpl).
• cli 0.4.1 → 0.4.2 carrying the template-pin change. No source change
  to CLI commands.

@omit-design/dev-server 0.3.0

[preset-mobile 0.4.0 + cli 0.4.2] - 2026-05-11 — Peer dep follow-up

Fixed

• preset-mobile bumped 0.3.0 → 0.4.0 so its peerDependencies.@omit-design/engine
  range (^0.4.0) reaches npm. The 0.4.0 release PR (#8) updated the peer
  locally but didn't republish preset-mobile, leaving npx omit-design init
  failing with ERESOLVE because the published preset-mobile@0.3.0 still
  declared engine ^0.3.0. Republishing under 0.4.0 (no source change other
  than the peer range — breaking by SemVer) fixes the install chain.
• scaffold template pin @omit-design/preset-mobile ^0.3 → ^0.4 (in
  templates/init/package.json.tmpl).
• cli 0.4.1 → 0.4.2 carrying the template-pin change. No source change
  to CLI commands.

@omit-design/cli 0.5.1

[preset-mobile 0.4.0 + cli 0.4.2] - 2026-05-11 — Peer dep follow-up

Fixed

• preset-mobile bumped 0.3.0 → 0.4.0 so its peerDependencies.@omit-design/engine
  range (^0.4.0) reaches npm. The 0.4.0 release PR (#8) updated the peer
  locally but didn't republish preset-mobile, leaving npx omit-design init
  failing with ERESOLVE because the published preset-mobile@0.3.0 still
  declared engine ^0.3.0. Republishing under 0.4.0 (no source change other
  than the peer range — breaking by SemVer) fixes the install chain.
• scaffold template pin @omit-design/preset-mobile ^0.3 → ^0.4 (in
  templates/init/package.json.tmpl).
• cli 0.4.1 → 0.4.2 carrying the template-pin change. No source change
  to CLI commands.

@omit-design/cli 0.5.0

[preset-mobile 0.4.0 + cli 0.4.2] - 2026-05-11 — Peer dep follow-up

Fixed

• preset-mobile bumped 0.3.0 → 0.4.0 so its peerDependencies.@omit-design/engine
  range (^0.4.0) reaches npm. The 0.4.0 release PR (#8) updated the peer
  locally but didn't republish preset-mobile, leaving npx omit-design init
  failing with ERESOLVE because the published preset-mobile@0.3.0 still
  declared engine ^0.3.0. Republishing under 0.4.0 (no source change other
  than the peer range — breaking by SemVer) fixes the install chain.
• scaffold template pin @omit-design/preset-mobile ^0.3 → ^0.4 (in
  templates/init/package.json.tmpl).
• cli 0.4.1 → 0.4.2 carrying the template-pin change. No source change
  to CLI commands.