EN Versions and Compatibility

Version baseline, compatibility and upgrades

English · Türkçe · Languages / Diller

Scope: JSON API Forge 0.5.1 · Source review: 17 September 2026 · Language: English

This Wiki describes the v0.5.1 ecosystem reviewed on 17 September 2026. Branch tips can move; source links are pinned to these complete SHAs.

Component	Branch	Reviewed commit
Server	main	356106c6610ce817fb9dfb03e391c85dd1726b24
SDK	python-library	9507fa902838f66400a603cea22b271a79d4eb9c
Editor	Editor	a4b3bff9120442533da957621684f34a65fcf15a
Examples	exampleApps	9c41f781449127c3c1ca39d41f90381c08a58abf

The v0.5.1 release was observed as published on 17 September 2026. Its tag points to main; it is not a common monorepo tag containing the other three product trees. Assets built from different branches can be attached to one GitHub Release.

Compatibility matrix

Contract	Current value	Review when it changes
Server/SDK/Editor version	0.5.1	Installation, packages and behavior documentation
Python test range	3.10–3.14	pyproject, CI and binary wheels
Minimum Qt	6.4	Compiler/ABI/WebEngine/packaging
Graph schema	1	Graph format and compiler
Plugin API	2; IID /2.0	Native rebuilds and manifests
Control plane	/__forge/editor/v1	Authentication, models, SDK and UI
Application API prefix	Application-defined	SDK helper and route contracts

Notable v0.5.1 behavior

The release continues v0.5.0 visual editing/collaboration and tightens JWKS/HTTP egress, DNS-rebinding boundaries, linear-time regex, URL/header/ICE metadata and SDK input validation. JSON hot reload and app fault isolation are part of the current CLI/runtime path. The Editor branch also includes workflow and installer-layout fixes under version 0.5.1.

Looser patterns, headers or URLs accepted previously may now be rejected. Do not assume a patch version requires no configuration review.

Upgrade workflow

1. Record current server/SDK/Editor commits and artifact filenames.
2. Back up app/, business/internal databases, media/attachments and secrets consistently.
3. Install official new source in a separate environment instead of blindly extracting over production.
4. Validate real configuration with secrets supplied through the proper environment.
5. Run forge validate, doctor --production, route/OpenAPI comparisons and migration rehearsals.
6. Test authentication, tenants/owners, idempotency replay, realtime, Editor session/save and SDK contracts.
7. Update affected Wiki pages using the maintenance map.
8. During rollout, check observability and whether data/schema compatibility permits returning to older binaries.

Observed documentation/distribution differences

Topic	Observation	Wiki treatment
SDK DELETE retry	Older prose differs from code	PUT/DELETE are method-eligible without a key
Editor settings menu	Older EDITOR.md differs from UI	Use Settings → Network and editor settings…
postgres-api preset	Name suggests PostgreSQL	Explain SQLite fallback without another URL
forge init	README suggests repeated use	Explain existing-file refusal and force rotation
Release checksums	Sidecars absent from reviewed list	Use source installation for the first run
SDK wheel name	py3-none-any_lib.whl	Install the verified source commit

These are documentation accuracy notes, not source-code fixes made during this task. Revise/remove them when later releases change the behavior. See the release asset snapshot.

Sources and verification

This page describes the behavior at the pinned commits below. Recheck these contracts when upgrading.

• main/CHANGELOG.md
• python-library/json_api_forge/options.py
• Editor/editor/src/MainWindow.cpp
• main/framework/cli.py

---

English home · All English pages · Version maintenance