Note
We're happy to announce the latest update of Portway. This release focuses on authentication performance, telemetry reliability, and UI consistency. Backup your application folder before upgrading and follow the migration steps below.
Fixes in v1.5.5:
- Dependencies: Various packages have been upgraded to their latest version.
New features in v1.5.x:
- Support for Model Context Protocol (MCP) – Expose your endpoints natively or just chat without leaving Portway
- Standardized Response Types – Introduced
PortwayResponse.csandPortwayResultsfor consistent API responses. - OpenTelemetry Instrumentation – Added telemetry for monitoring performance and errors.
- Improved Concurrency – Enhanced thread safety and resource management.
- Refactored DI – Simplified service registration with extension methods.
- Schema Standardization – Updated schemas for webhooks and file endpoints.
Migration guide
As 1.5.0 has introduced breaking changes, please follow the following steps for a safe upgrade path:
- Update Docker configurations. If you are running Portway in a container, please check the updated documentation regarding the ASP.NET port mappings, as these have changed.
- Configure Web UI access. If you plan to access the admin console externally, ensure you explicitly enable external traffic routing in your (
appsettings.json) settings. - Verify your File & Webhook endpoints. The structure of these have changed slightly,
Check our documentation for guidance. If you encounter issues, open a new Issue.
Check our documentation for guidance. If you encounter issues, open a new Issue.
Full Changelog: v1.5.4...v1.5.5