Warning
We're happy to announce the latest update of Portway v1.5.2. This release introduces standardized response types, OpenTelemetry instrumentation, improved concurrency, and refactored dependency injection. Backup your application folder before upgrading and follow the migration steps below.
Fixes in v1.5.2:
- Standardized response types and casing for consistency across APIs.
- Removed redundant code and deduplicated logic in core services.
- Improved concurrency and reliability:
- Replaced
Task.RunwithChannelloops in file watchers. - Added proper disposal of resources and cancellation support.
- Enhanced thread safety in
SqlConnectionPoolServiceandTokenService.
- Replaced
- Added OpenTelemetry instrumentation for monitoring and observability.
- Refactored dependency injection with dedicated extension methods.
- Standardized webhook and file endpoint schemas for clarity and consistency.
New features in v1.5.2:
- 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
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.
Full Changelog: v1.5.1...v1.5.2