Releases: cogsol/cogsol-framework
Releases · cogsol/cogsol-framework
v0.2.1
What's new
This release improves authentication and configuration handling, strengthens migration reliability, and updates documentation for setup and usage.
Added
- Optional Azure AD B2C client-credentials authentication in
CogSolClientwith automatic bearer token acquisition.
Changed
- Standardized API key configuration on
COGSOL_API_KEY. CogSolClientnow sends bearer tokens when configured and retries once after refreshing credentials on401.- Centralized API base URL resolution via shared helpers with support for
COGSOL_ENV,COGSOL_API_BASE, andCOGSOL_CONTENT_API_BASE. - Fallback to legacy cognitive/content API base URLs when auth credentials are not configured.
startagentnow validates generated slugs and class names more strictly, and generated templates no longer append a redundantChatsuffix tochat_name.- Tool parameter sync now preserves
itemsmetadata for array parameters. startprojecttemplate.env.examplenow includes API key and optional auth credential placeholders.- Runtime dependencies now include
msalandPyJWT.
Fixed
- Migration ordering for agent dependencies to avoid first-run failures.
startprojectnow includes an activeExampleToolimplementation by default.- Migration tool payload sync now preserves configurable tool flags instead of hardcoding them.
- Migration finalization now rolls back partially created API objects when sync fails.
- Tool migration sync now preserves helper methods, double quotes, and multiline helper/run signatures more reliably.
- Improved chat banner alignment and terminal output rendering.
Documentation
- Updated environment variable and authentication docs to use
COGSOL_API_KEY. - Removed outdated “no external dependencies” statements.
- Clarified that
documentationin README examples is only a sample topic name. - Updated retrieval-tool examples to instantiate retrieval definitions.
- Added explicit
.venvsetup instructions. - Clarified clone-directory setup steps.
Upgrade notes
- Update the package to
0.2.1. - Review your environment variables and use
COGSOL_API_KEYinstead ofCOGSOL_API_TOKEN. - If you use custom auth setup, verify your
COGSOL_AUTH_CLIENT_IDandCOGSOL_AUTH_SECRETconfiguration.