Kanera changelog

version

4.2.0 → 4.3.0

website_url

— → https://www.kanera.app

https://raw.githubusercontent.com/happendev/Kanera/HEAD/AGENTS.md

− - Add user-visible changes to `CHANGELOG.md`. Keep succinct.+ - Add only substantial user-visible changes or fixes to `CHANGELOG.md`; skip minor tweaks.+   Keep entries succinct but useful for end users.+ ## MCP release documentation+ Every MCP release must update Kanera-site in the same release process. In Kanera-site, run+ `npm run docs:mcp-sync` against the release checkout (`KANERA_PRODUCT_REPO` overrides `../Kanera`).+ This regenerates the tool inventory, server card, portable plugin version, and discovery catalog.+ Review the MCP guides for changed behavior, regenerate translations with `npm run i18n:generate`,+ and run `npm run docs:mcp-check`, `npm run i18n:check`, and `npm run test:agent-discovery`.+ Commit, merge, and deploy the site changes alongside the MCP service before publishing the+ `mcp-vX.Y.Z` registry release. Publishing checks the public deployed metadata and inventory against+ the release source (`node scripts/check-mcp-site.mjs` in Kanera; `KANERA_SITE_URL` supports local+ verification). Site CI also checks committed metadata against the product source.

https://raw.githubusercontent.com/happendev/Kanera/HEAD/AGENTS.md

+ - Before adding complexity for speculative race conditions, security edge cases, or unlikely+   failures, explain the concrete failure mode, its likelihood, and the implementation and+   maintenance cost. Get user approval before materially expanding scope for theoretical+   robustness. Address demonstrated problems within the agreed scope directly.

version

4.1.0 → 4.2.0

https://raw.githubusercontent.com/happendev/Kanera/HEAD/AGENTS.md

− - Workspace membership grants access to every board; `board_members` grants cross-organisation guest−   access to specific boards.− - A user belongs to exactly one organisation (`clients` row) and email is globally unique.− - Add user-visible changes to `CHANGELOG.md`.+ - Ordinary users access board content through `board_members`, including cross-organisation guests.+   Workspace and organisation admin authority materializes pinned board memberships; organisation+   owners/admins also have an explicit access override. Workspace membership alone does not grant board access.+ - A user can belong to multiple organisations through `client_members`; email is globally unique.+   `users.clientId` remains the original storage/media anchor, while `activeClientId` selects the default organisation.+ ## Work assigned through Kanera cards+ When the user asks you to carry out a specific Kanera card, keep the card updated as part of the+ assignment. Use the connected Kanera skill/instructions: read the card and relevant comments,+ record the original list ID/name/meaning, check for another live agent run, start your run before+ substantive work, and move to the board's+ actual active list. Update progress at milestones and at least every ten minutes. On a blocker,+ record what is needed in both the run and a card comment, and use the appropriate waiting list.+ Before your final reply, post an outcome comment with changes, verification results, relevant+ PR/commit/artifact links, and remaining work; end the run appropriately. Before moving the card,+ re-read the card and board. Consider the original list, available lists and their meanings,+ completed work and remaining work; choose the list that reflects the card's actual state in this+ board's workflow. Returning to the original list may be appropriate but is not automatic. Do not+ assume list names or choose by list order or the in-progress flag alone. Explain the choice in the+ comment. If unclear, leave the list unchanged, save other tracking and ask. A successful run may+ cover only part of a card; complete the card only when the agreed workflow permits it and its+ criteria are met. Verify the saved comment, run status, and card list; report any failed write.+ Reading or exploratory planning alone causes no tracking writes; explicit user restrictions win.+ This applies to real-data work the user assigns, and does not authorise using production Kanera+ for local verification or updating an unrelated card.+ - Add user-visible changes to `CHANGELOG.md`. Keep succinct.

https://raw.githubusercontent.com/happendev/Kanera/HEAD/AGENTS.md

− CLAUDE.md+ Guidance for AI coding agents in this repository. `CLAUDE.md` imports this file; edit this one.+ Area-specific rules live next to the code and load when you work there:+ [`apps/api/AGENTS.md`](apps/api/AGENTS.md), [`apps/web/AGENTS.md`](apps/web/AGENTS.md), and+ [`e2e/README.md`](e2e/README.md). Reusable procedures belong in `.agents/skills/`.+ ## Product+ Kanera is an opinionated project management tool where every board inside a workspace shares the same+ lists and custom fields.+ ```text+ Organisation (client)+   └─ Workspace+        └─ Board+             └─ Card+ ```+ Durable invariants. Code anywhere in the stack may rely on these, so comment at the point of use when+ you do:+ - Lists and custom fields are workspace-scoped, not board-scoped.+ - Workspace membership grants access to every board; `board_members` grants cross-organisation guest+   access to specific boards.+ - A user belongs to exactly one organisation (`clients` row) and email is globally unique.+ - Onboarding runs when `me.hasWorkspace === false`.+ - Every user-facing string is translated (en-US, en-GB source, es, pt-BR, fr, de, ja, nl, nb, zh-CN, zh-TW). The account's+   `users.locale` decides the language of the web app, emails and push.+ - `KANERA_DEPLOYMENT_MODE=hosted` turns on billing, plans and tier limits; self-hosted has none. Check+   which mode a change applies to.+ ## Repo shape+ ```text+ apps/api/        Fastify + Socket.IO + Drizzle; four processes (see apps/api/AGENTS.md)+ apps/web/        Angular standalone app+ apps/admin-web/  Internal admin console, served by the admin API+ apps/mcp/        MCP tool layer over the public API+ apps/cli/        `kanera` CLI; a second transport onto the MCP tool layer+ packages/sdk/    `@kanera/sdk`; self-contained public API client, no workspace deps+ packages/shared/ Shared schema, DTOs, and realtime event types+ e2e/             Playwright end-to-end suite+ ```+ `@kanera/shared` is the source of truth shared by server and client: `/schema` (Drizzle tables and+ inferred types), `/dto` (Zod request/response schemas), `/events` (Socket.IO contracts). Change a+ contract there first, then align the server and client in the same change.+ ## Commands+ Run everything from the repo root.

Showing the first 40 of each.

version

4.0.0 → 4.1.0

version

3.2.0 → 4.0.0