Skip to content
Motir
Start free

moooon

Motir

Vibe your whole project. Bring an idea — Motir's three AI layers plan it, track it, and ship it, end to end. You're looking at Motir, built in Motir.

  • Vibe Project
  • Open Source
  • AI Agent
  • AI Loop
1
requests
0
upvotes
145
planned
1,361
shipped
Follow  — continues on app.motir.co
Request a featureAtom feed

← Motir · Work items

MOTIR-4051Done

Bump @motir/design-system to 0.1.3 — the commit `design-system-v0.1.3` is cut from

One file, one line, one pull request: packages/design-system/package.json "version": "0.1.2" → "0.1.3". Nothing else changes.

MOTIR-3997's @scope rewrite is already in the package's SOURCE on origin/main — packages/design-system/theme.css returns 69 for grep -c '@scope'. The PUBLISHED 0.1.2 predates it (cut from e76d1afdd828e88b69b29e1c65260a8624d51fc2, published 2026-08-30T20:34:31Z). The fix is in the source and not in the artifact, and the only thing that closes that gap is a new version number.

Why the bump is its own card. .github/workflows/release-design-system.yml fires on a design-system-v<x.y.z> tag and fails fast unless the tag equals package.json's version; packages/design-system/README.md § Releasing states the procedure as bump → merge → tag. The tag can only be pushed once THIS pull request has merged, which is a human act in manual merge mode — so the cut is MOTIR-3999, not this card, and the boundary between them is a merge.

Acceptance criteria

  • packages/design-system/package.json reads "version": "0.1.3", and the pull request's diff touches that file and no other.
  • Pre-flight the tarball this version will publish, so the release does not discover a packaging gap: pnpm --filter @motir/design-system build, then in packages/design-system run npm pack and read what came out — tar -xzOf motir-design-system-0.1.3.tgz package/theme.css | grep -c '@scope (' must be 69 and no bare [data-style='X'] [data-surface= descendant rule remains outside the four .style-vignette … > .sv-canvas ones. This is evidence for THIS pull request; the PUBLISHED tarball is what the cut checks, and a local pack is not that.
  • pnpm --filter @motir/design-system build and pnpm --filter @motir/design-system test pass locally. Everything suite-wide is the pull request's own CI to report, not this run's to re-run.
  • The pull-request body names MOTIR-3999 as the card that cuts the tag once this merges, so whoever merges knows a second step is owed.
  • ORDERING — every criterion reads on THIS branch. Nothing here reads on the tag, on npm, or on motir-marketing.