update OV runtime to 2026.5 dev

[dtrawins]

🛠 Summary

🧪 Checklist

• Unit tests added.
• The documentation updated.
• Change follows security best practices.
  ``

[Copilot]

🔵 Needs a closer look

The PR pins to nightly/dev OpenVINO artifacts while stamping OVMS image/package versioning as stable-looking 2026.5.0, which should be clarified or aligned to avoid misleading release tags.

Pull request overview

Updates OVMS build/release metadata and dependency pins to align with OpenVINO / OpenVINO GenAI 2026.5 development artifacts, ensuring packaging and functional checks expect the new runtime versions.

Changes:

• Bump OVMS version/tag strings to 2026.5.0 across Windows script, Makefile, and Dockerfiles.
• Update OpenVINO / Tokenizers / GenAI source commit pins and switch Linux/Windows binary URLs to a 2026.5 nightly build.
• Refresh expected packaged library filename/symlink lists and demo export-model Python requirements for 2026.5.

File summaries

File	Description
windows_set_ovms_version.py	Updates default OVMS project version used for Windows builds.
versions.mk	Moves OpenVINO/Tokenizers/GenAI pins and binary URLs to 2026.5 nightly artifacts.
tests/file_lists/lib_files.txt	Updates expected OpenVINO/GenAI shared library SONAME/version symlinks for 2026.5.
tests/file_lists/lib_files_python.txt	Updates expected OpenVINO/GenAI shared library entries for Python packaging checks.
Makefile	Bumps PRODUCT_VERSION to 2026.5.0, impacting Docker build args/version stamping.
Dockerfile.ubuntu	Updates dist-info metadata/version strings and default PROJECT_VERSION to 2026.5.0.
Dockerfile.redhat	Updates dist-info metadata/version strings, default PROJECT_VERSION, and image label version to 2026.5.0.
demos/common/export_models/requirements.txt	Pins demo export dependencies to OpenVINO 2026.5 nightly wheels.
create_package.sh	Updates openvino-genai dist-info directory/metadata version strings to 2026.5.

Review details

Suppressed comments (1)

Makefile:203

• The build is now pinned to OpenVINO GenAI nightly artifacts (2026.5.0.0.dev20260903 in versions.mk), but the generated OVMS project/version string is bumped to a stable-looking "2026.5.0" here. This is potentially misleading for published image/package versioning and makes it unclear whether the release is intended to track a nightly/dev runtime; consider either including a dev/nightly suffix in PRODUCT_VERSION/PROJECT_VERSION or clarifying via version variables used for tagging.

PRODUCT_VERSION ?= "2026.5.0"
PROJECT_VER_PATCH =

$(eval PROJECT_VER_PATCH:=`git rev-parse --short HEAD`)
$(eval PROJECT_VERSION:=${PRODUCT_VERSION}.${PROJECT_VER_PATCH})

• Files reviewed: 9/9 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.