Changelog
This page explains where WingGate changes are published today, what to check before upgrading a deployment, and how this page will evolve once tagged releases begin.
WingGate is currently at version 0.1.0 in an early stage. There are no tagged releases and no per-version changelog entries yet — this page deliberately does not invent any.
Where changes are published
All changes are recorded on this page as they land. Entries are grouped by type: feat introduces a capability, fix corrects behavior, docs updates documentation, and so on.
This page is the single place to follow what changed over time.
Current version state
The software is at version 0.1.0. Public protocols and cross-component contracts are described by the compatibility page and the API and protocol reference article; compatibility constraints are versioned with the code and covered by the docs.
Breaking changes during this stage are visible in the documentation that owns the affected contract. There is no separate migration guide yet.
What to check when upgrading
Operators upgrading a self-hosted deployment should follow the connector deployment article, which describes component upgrade order and rollback boundaries.
Runner artifacts are built as static x86_64 Linux binaries and ship with a SHA-256 digest signed by an offline Ed25519 release key, so asset-side runner payloads can be verified before installation.
How security fixes are disclosed
Security-relevant fixes are disclosed on this page and in the documentation that owns the affected contract. If you run a deployment, check this page so you see security fixes as they land.
Maintenance source and ownership
This page and the release discipline it describes are maintained by the project maintainers. This page is the single source of truth for change history.
When the project starts tagging releases, this page will be updated to list per-version entries with their compatibility and migration notes.