Releases
Use release pages to understand what changed, which Unreal Engine versions are supported, and whether an update requires action from your project.
Dynaros is still early, so some release history is currently pre-release context rather than formal versioned release notes.
Release Maturity
Section titled “Release Maturity”Dynaros uses maturity labels to describe how safe a product or feature is to depend on.
- Stable means Ganivyr is prepared for developers to rely on the product or public feature.
- Experimental means the feature is usable, but its API, behavior, design, or workflow may still change.
- Deprecated means the feature remains available for compatibility but should not be used for new work.
Stable does not mean perfect. It means the feature has a defined responsibility, intentional public APIs, documentation, supported engine context, and a support path.
Version Numbers
Section titled “Version Numbers”Formal Dynaros releases use semantic versioning:
MAJOR.MINOR.PATCH- PATCH releases contain bug fixes, documentation corrections, and non-breaking polish.
- MINOR releases add functionality while preserving stable public APIs.
- MAJOR releases are reserved for necessary breaking changes.
Unreal Engine compatibility is tracked alongside product version.
Example:
Dynaros Interaction 1.4.2 - supports Unreal Engine 5.8.xWhat Release Notes Should Tell You
Section titled “What Release Notes Should Tell You”Release notes should make it clear what changed and whether you need to do anything.
Common sections include:
- Added
- Changed
- Fixed
- Deprecated
- Removed
- Known Issues
- Compatibility Notes
Breaking or behavior-changing updates should include migration guidance instead of expecting you to reverse-engineer the change from source.
Version-Aware Docs
Section titled “Version-Aware Docs”As Dynaros matures, docs may include selectors for:
- Dynaros product version
- Unreal Engine version
When those selectors are available, choose the versions that match your project. Installation steps, APIs, compatibility notes, and migration instructions may differ between releases.
Interaction Pre-Release History
Section titled “Interaction Pre-Release History”August 2026 - Architecture and Portability Pass
Section titled “August 2026 - Architecture and Portability Pass”Interaction has gone through an early extraction and portability pass.
Highlights:
- Extracted the interaction code from the original GAM 465 project into a reusable Unreal Engine plugin.
- Added
UInteractorComponent,UInteractableComponent,IInteractable, andAInteractableActoras the initial reusable architecture. - Moved interaction prompt UI into the plugin and removed project-specific character casting.
- Added Enhanced Input compatibility.
- Added the dedicated
LogInteractionSystemlogging category. - Packaged the plugin and integrated it into a separate Unreal Engine 5.8 GAM 312 project to verify portability.
- Migrated ore and herb actors toward the component/interface interaction pattern.
- Expanded the plugin specification around lifecycle, responsibility boundaries, extension points, multiplayer direction, debugging expectations, and future feature candidates.
This is pre-release history, not a formal public version. The first formal version number should be assigned when the release and distribution strategy is finalized.