Releases: aiperceivable/flask-apcore
Releases · aiperceivable/flask-apcore
Release 0.3.1
Changed
- Rebrand: aipartnerup → aiperceivable
Release 0.3.0
Added
- JWT authentication for MCP endpoints:
--jwt-secret,--jwt-algorithm,--jwt-audience,--jwt-issuerCLI flags and correspondingAPCORE_SERVE_JWT_SECRET,APCORE_SERVE_JWT_ALGORITHM,APCORE_SERVE_JWT_AUDIENCE,APCORE_SERVE_JWT_ISSUERconfig settings (requiresapcore-mcp>=0.7.0, HTTP transports only). - Minimum secret length validation (16+ characters) for HMAC algorithms (HS256/HS384/HS512).
Changed
- Bump
apcore-mcpoptional dependency from>=0.6.0to>=0.7.0.
Release 0.2.1
Release version 0.2.1
See CHANGELOG.md for details.
Release 0.2.0
Added
- MCP Serve Explorer passthrough:
--explorer,--explorer-prefix,--allow-executeCLI flags and correspondingAPCORE_SERVE_EXPLORER,APCORE_SERVE_EXPLORER_PREFIX,APCORE_SERVE_ALLOW_EXECUTEconfig settings, forwarded toapcore_mcp.serve().
Fixed
- Preserve
http_methodandurl_rulein RegistryWriter metadata. - Serialize Pydantic models correctly in call endpoint output.
Changed
- Remove Flask Blueprint Explorer (
/apcore/routes,flask_apcore.webmodule,APCORE_EXPLORER_*config settings) in favour of the apcore-mcp Tool Explorer available viaflask apcore serve --explorer. - Remove JSON / OpenAPI output writers (superseded by apcore-mcp explorer).
- Bump
apcore-mcpoptional dependency from>=0.4.0to>=0.5.1.
Release 0.1.0
Added
- Initial release of
flask-apcore. - Flask extension for apcore AI-Perceivable Core integration.
- App-scoped Registry, Executor, and ContextFactory wrappers following Flask multi-app best practices.
- Direct registration of scanned modules into the apcore Registry via
RegistryWriter. - Support for user and observability middlewares, ACL, and executor config.
- Schema backends for Marshmallow, Pydantic, and type hints.
- Comprehensive test suite including async test support.
- Developer tooling: pytest, pytest-flask, pytest-asyncio, ruff, mypy, pre-commit, coverage.