Conversation
* feat: refresh app icon to the Mimir monogram mark Replace the placeholder favicon with the black/purple Mimir square mark used across brand surfaces, in both the Tauri app and the landing package. * feat(core): support custom MCP agent targets in setup and install-skill Generalize the previously hardcoded Claude/Codex/Kimi/OpenCode/Cline MCP helper generation into a configurable agentHelpers list. Add --agents, --mcp-name, --mcp-command, and --mcp-arg to `mimir setup` and `mimir install-skill` so an arbitrary MCP-compatible agent can be targeted without a source change.
…32) * feat: pin Node.js toolchain with mise Replace the Node version hardcoded across CI workflows with a single mise.toml pin, installed via jdx/mise-action in ci.yml and native-app-build.yml. npm-publish.yml keeps actions/setup-node since it also wires npm registry auth. pnpm stays pinned via Corepack's packageManager field, not duplicated in mise.toml. * docs: add llms.txt and context7.json for LLM-facing discovery Prepare the repo to be indexed by Context7: llms.txt follows the llmstxt.org convention and links the docs relevant to consuming Mimir as a library/CLI/MCP server (excludes Tauri app, landing, and licensing docs, which aren't part of that surface). context7.json scopes the crawler away from generated/private directories and adds a few correctness rules. Also documents the direct skills.sh install path for the bundled mimir skill. * fix(ci): install mise via curl instead of jdx/mise-action jdx/mise-action is blocked by this repo's Actions permissions policy (allowed_actions: selected, restricted to actions/*, github/codeql-action/*, and verified creators), which caused a startup_failure on every workflow run. Install mise with the official curl script in a plain run: step instead, which isn't subject to the uses: allowlist.
pnpm is only relevant to contributors building this monorepo (already covered in CONTRIBUTING.md); people consuming the published @jcode.labs/mimir and @jcode.labs/mimir-tts packages may use any package manager. Flip the README, docs/agent-integration.md, docs/troubleshooting.md, and the per-package READMEs to lead with npm/npx, keeping pnpm as a documented alternative only where it was already explicitly labeled as such. Also pin Rust via mise.toml (only needed for packages/mimir-app's Tauri shell, previously undocumented), add a `bootstrap` script (`mise install && pnpm install`) as the one-command onboarding path, and drop the now-redundant dtolnay/rust-toolchain step from native-app-build.yml in favor of mise installing both Node and Rust.
Mention mimir audio's spoken-summary path in the Developer Use Cases table, alongside the existing use cases, not as the headline feature.
feat(setup): add semantic setup preload
Reconcile squash-merged release history: main #33 squashed develop's #31/#32 and carried a main-only release commit whose substantive infra (npm-publish, ci, codeql, releaserc) is already identical on develop. develop is a verified content superset, so keep develop's tree and record main as a parent to unblock the develop -> main release merge.
…velop chore: back-merge main release history into develop
|
🎉 This PR is included in version 1.2.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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
Promote the
developintegration branch tomainto cut a new npm release.What's included
mimir setup --semantic/ models preload path)Release
Merging to
maintriggers the protectedRelease npmworkflow (semantic-release). Thefeatcommits bump the minor version;@jcode.labs/mimir-ttspublishes before@jcode.labs/mimir.Validation
CI Quality gate + CodeQL green on the source PR (#34). Release gate (
pnpm validate) runs again in the release workflow before publishing.