TightWiki v2.43.0
Downloads
NuGet package: TightWiki.Plugin (see all on NuGet).
Release notes
👉 Please see upgrade notes at the bottom before upgrading an existing installation 👈
For plugin development, be sure to check out the NuGet Package 📦
📌 This is a substantial upgrade that includes some important long overdue changes, primarily moving the file attachments outside if the SQLite database. For this reason, you should backup your SQLite databases prior to upgrading because reverting to the previous version without the backups is not a simple task.
See release 2.42.0 for the other major changes in this release.
📢 This release is almost wholly the work of @eMukator, so thanks man!
📢 This release below this one was due to the contributions of @maidis, thought I should mention that too! 👍
New 🎉
- Personal API tokens. Users can create, list and revoke named API tokens from their profile (Profile → API Tokens). A token is shown once when created; only its SHA-256 hash is stored. A token only identifies the user and grants no extra permissions.
- REST API (
/v1/). JSON endpoints authenticated withAuthorization: Bearer <token>:GET /v1/search: search pagesGET /v1/pages/{navigation}: read a page as markup, HTML or plain text, optionally at a given revisionGET /v1/pages/{navigation}/revisions: revision historyGET /v1/namespacesandGET /v1/namespaces/{name}/pages: namespaces and their pagesGET /v1/tags/{tag}/pages: pages with a tagPOST /v1/pagesandPUT /v1/pages/{navigation}: create a page and save a new revision
- MCP endpoint (
/mcp). AI assistants can search, read, create and update pages through the Model Context Protocol, using the same API tokens. Tools:search_pages,get_page,get_page_revisions,list_namespaces,list_namespace_pages,list_tag_pages,get_wiki_syntax_help,create_page,update_page. - New settings (Functionality), all disabled by default:
- Enable API turns on API tokens and
/v1/. - Enable MCP turns on
/mcpand requires Enable API. - Allow API Writes allows creating and editing pages through the API and MCP.
- Enable API turns on API tokens and
- Pages saved through the API or MCP require a change summary and are marked
[API]or[MCP]in the page history.
Changed 😎
- The web editor and the API now share one page-save routine, so both apply the same checks: permissions, protected pages, name validation and revision conflicts.
- Deleting a user account, either by the user or by an administrator, now also deletes that user's API tokens.
TightWiki.Plugin:TwConfigurationaddsEnableApi,EnableMcpandAllowApiWrites.- New dependency:
ModelContextProtocol.AspNetCore2.4.0.
Upgrade notes 👀
- The site's application pool user needs write permission on
data/Attachments(or whereverAttachmentPathpoints). - After upgrading,
pages.dbstays its original size even once all attachments have moved out of it. It is not shrunk automatically. - When upgrading an existing site, do not copy the release's
datafolder over your own. The release'sdata/Attachmentsholds the built-in help images, and its files would overwrite your attachments that have the same numbers.