Where to Find OpenWork Release Notes: A Complete Guide

OpenWork maintains release notes in two synchronized locations: the changelog/ directory on the dev branch and the GitHub Releases page.

As an open-source framework for agent management, OpenWork (different-ai/openwork) keeps its version history transparent and accessible. Whether you're debugging an upgrade, auditing changes, or automating deployments, knowing exactly where to find release notes saves time and prevents misconfiguration.

The Two Primary Sources for OpenWork Release Notes

Changelog Directory: The Authoritative Source

The changelog/ folder in the repository root contains the definitive release documentation. Each version gets its own Markdown file with a predictable naming convention.

Browse the directory at: changelog/

Recent files include:

• release-tracker-2026-08-18.md – latest release notes (as of the dev branch state)
• release-tracker-2026-03-15.md – previous release

These files contain full change descriptions, migration instructions, and breaking change alerts. When in doubt, check here first—the changelog directory is the source of truth that other locations reference.

GitHub Releases Page: The Entry Point for Most Users

Every Git tag triggers a GitHub Release entry. These pages provide:

• Condensed summaries of each version
• Direct links to corresponding changelog files
• Downloadable assets and tarballs
• Tag references (vX.Y.Z) for CI/CD pipelines

Access at: Releases

The GitHub Releases page stays synchronized with the changelog/ directory. Use it for quick overviews; drill into the linked Markdown files for comprehensive details.

Programmatically Accessing OpenWork Release Notes

Fetch Latest Release via GitHub API

Retrieve release metadata programmatically using the GitHub REST API:

import fetch from 'node-fetch';

const url = 'https://api.github.com/repos/different-ai/openwork/releases/latest';

const getLatestRelease = async () => {
  const resp = await fetch(url, {
    headers: { 'Accept': 'application/vnd.github.v3+json' },
  });
  const data = await resp.json();
  console.log('Version:', data.tag_name);
  console.log('Release notes URL:', data.html_url);
};

getLatestRelease();

This returns structured JSON including tag_name, body (release notes), html_url, and asset download URLs.

Open Specific Release in Browser

From your terminal, jump directly to any tagged release:

TAG=v2.4.1
open "https://github.com/different-ai/openwork/releases/tag/${TAG}"

Replace v2.4.1 with your target version. This pattern works across macOS (open), Linux (xdg-open), or Windows (start).

Link to Changelog from Documentation

When writing internal docs or pull request descriptions, reference the canonical Markdown file:

See the full changes in
[release-tracker-2026-08-18.md](https://github.com/different-ai/openwork/blob/dev/changelog/release-tracker-2026-08-18.md)

Deep-linking to specific changelog files ensures your references remain valid even if the Releases page UI changes.

Key Files Related to OpenWork Releases

File	Purpose	Location
changelog/	Per-release Markdown notes	changelog/
release-tracker-2026-08-18.md	Most recent release example	[release-tracker-2026-08-18.md](https://github.com/different-ai/openwork/blob/dev/changelog/release-tracker-2026-08-18.md)
package.json	Version field mapping to Git tags	[package.json](https://github.com/different-ai/openwork/blob/dev/package.json)
AGENTS.md	Architecture notes on release impacts	[AGENTS.md](https://github.com/different-ai/openwork/blob/dev/AGENTS.md)
README.md	High-level overview with release links	[README.md](https://github.com/different-ai/openwork/blob/dev/README.md)

Understanding these files helps trace how version numbers in package.json propagate to Git tags and ultimately to the release notes you consume.

Summary

• Primary location: changelog/ directory on the dev branch contains full Markdown release notes
• Secondary location: GitHub Releases page offers quick overviews and tag-based access
• Naming pattern: Files follow release-tracker-YYYY-MM-DD.md convention
• API access: Use https://api.github.com/repos/different-ai/openwork/releases/latest for automation
• Cross-reference: Releases page links to changelog files; both stay synchronized

Frequently Asked Questions

How do I find the latest OpenWork release notes?

Check the changelog/ directory for the most recently dated release-tracker-*.md file, currently release-tracker-2026-08-18.md. Alternatively, visit the Releases page and click the top entry.

Are OpenWork release notes available in machine-readable format?

Yes. The GitHub API endpoint repos/different-ai/openwork/releases/latest returns JSON with structured release data including tag_name, body (the notes), and published_at timestamps. The changelog Markdown files themselves follow consistent formatting that parses well with standard Markdown processors.

What is the relationship between package.json version and release notes?

The version field in [package.json](https://github.com/different-ai/openwork/blob/dev/package.json) defines the current package version. When maintainers cut a release, they tag the repository with v${version} (e.g., v2.4.1), which generates a GitHub Release entry pointing to the corresponding changelog file in changelog/.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}