Software changes over time. Features are introduced, existing workflows improve, issues are resolved, and priorities evolve as products develop.
A changelog provides a transparent record of those changes. It helps users understand what has changed, when a change occurred, which areas may be affected, and whether any action is required.
The Runner changelog is intended to document actual product development rather than publish aspirational feature lists as completed releases.
What each update should explain
New capabilities
Describe functionality that has actually been released, what it enables, and any relevant availability requirements.
Improvements
Explain how an existing capability or workflow has changed and what users should expect to be different.
Fixes
Describe resolved issues in clear language, including the affected area where appropriate.
Compatibility and integrations
Document confirmed changes that affect supported integrations, requirements, permissions, or connected services.
Known limitations
Communicate important outstanding issues or limitations when appropriate, including any relevant workarounds.
A useful release note
Each published changelog entry should include:
- Release date.
- Version or release identifier, if applicable.
- Category of change.
- Clear description of the change.
- User impact or practical significance.
- Availability details or required actions, where relevant.
- Known limitations, where appropriate.
Entries should use language that readers can understand without needing to inspect source code.
Development transparency
A planned feature is not the same as an available feature.
Roadmap ideas, experiments, internal development work, and released functionality must be clearly distinguished. A feature should not be described as generally available unless its availability has been verified.
If the product is in early access, explain the current status honestly and identify any access limitations that are known.
Every change should be clear
Product updates will be documented here as Runner capabilities are released or materially changed. Each entry will explain what changed, when it happened, and what it means for users.
For product direction without release claims, see product roadmap and platform overview.