Releases: helyOSFramework/helyos_core
Releases · helyOSFramework/helyos_core
2.1.6
2.1.4
- Added yard ID in followers data and deleted_at filter in database request handler
- Fixed handling of wrong yard UID, request data setting, and RabbitMQ account delete errors.
- Improved the base image by reducing size and updating to Ubuntu Jammy.
2.1.0
Changes
- Microservices URLs must now be provided in full, including the endpoint. Note that helyOS core will no longer append the endpoint
/plan_job
. - The WebSocket topic "change_work_processes" has been renamed to "work_processes_update" for consistency.
- New fields have been included in the helyos database: run the DB migration.
Features
- Policy for Assignment Failure: Introduced three new policies:
FAIL_MISSION
,CONTINUE_MISSION
, andRELEASED_FAILED
. - Fallback Mission: Implemented a fallback mission for agents that fail an assignment.
- Filter Map Objects: Enhanced functionality to send filtered map objects as part of the microservice context.
- Instant Actions from microservices: Microservice responses in now able to trigger instant actions.
- Conditional Run of a Mission Step: Microservice responses can now select or skip the next microservice to be triggered.
- Bug Fixes: Various bug fixes to improve stability and performance.
2.1.0-rc
- IMPORTANT Change: Microservices URLs must now be provided in full, including the endpoint. Note that helyOS core will no longer append the endpoint
/plan_job
. - Policy for Assignment Failure: Introduced three new policies:
FAIL_MISSION
,CONTINUE_MISSION
, andRELEASED_FAILED
. - Fallback Mission: Implemented a fallback mission for agents that fail an assignment.
- Filter Map Objects: Enhanced functionality to send filtered map objects as part of the microservice context.
- Bug Fixes: Various bug fixes to improve stability and performance.
2.0.4
Release 2.0.4
This release introduces several improvements and bug fixes:
Strengthened Security: Dependencies have been updated and the Dockerfile has been refactored to enhance security.
Additional RabbitMQ and Postgres connections for agent visualization messages.
Improved Message Flow: The Time-To-Live (TTL) and prefetch values have been optimized.
Enhanced Log Messages: Log messages have been improved for better readability.
Optimized Log Collector: The log collector has been optimized to utilize the database more efficiently.
Database Constraints Status Checking: Ensure that your database has valid status values before performing the migration.
Expanded Test Coverage.
Dashboard bugs fixed.