chore(release): prepare memi 1.0.2 distribution#26
Merged
Conversation
PR #24 added pnpm + yarn install commands and excluded plugin/*.png from the tarball, which required bumping the npm version (1.0.0 -> 1.0.1) to publish. This commit syncs all release-gate-enforced version pins to 1.0.1 so main matches what's on npm. Files synced: - package.json + package-lock.json - server.json (3 places) - plugin/widget-meta.json - plugins/memoire/.codex-plugin/plugin.json - 12 examples/**/registry.json - examples/presets/starter/README.md - preview/changelog.html (regenerated from CHANGELOG.md) CHANGELOG: v1.0.1 entry covering the install-variants and pack-size-fix changes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Hero was already on the new brand from PR #21, but 32 references below the fold still said "Memoire" or "Mémoire" — anyone scrolling the npm page sees inconsistent branding. Also dropped two stale "0.16.3 ships..." prose pins that made the README look unmaintained. Preserved on purpose: - Two `Mémoire Studio_0.16.3_aarch64.dmg` filename examples — these are the actual Tauri-bundled DMG names; updating prose without rebuilding the app would create a misleading reference. - All `~/.codex/skills/memoire/`, `~/.hermes/skills/memoire/`, `plugins/memoire/`, `memoire.agent.yaml` paths — these are installed in user environments and renaming would break installs. `check:release` still passes (requiredReadmeTerms substrings all live in the unchanged hero). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
\`memi --help\` was printing \`Usage: memoire [options] [command]\` because the Commander program name was never updated during the rebrand. First-time users running --help after \`npm i -g @memi-design/cli\` saw the old brand. Also updated the program description from the old "Diagnose and improve real web apps..." to the new tagline that matches package.json: "Design-system memory for coding agents — pull tokens from Figma, generate shadcn-native components, audit Tailwind apps". Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Verification
Note: local npm auth is unavailable in this Codex shell (npm whoami returns 401), so publish should run through the repository workflow with NPM_TOKEN after merge.