text-to-CAD Release Notes: Where to Find Version History and Changelogs

text-to-CAD release notes are published exclusively through GitHub Releases, while the canonical version string is maintained in the VERSION file at the repository root.

The earthtojake/text-to-cad repository does not maintain a traditional CHANGELOG.md file. Instead, version history and detailed release documentation are tracked through a lightweight combination of a plain-text version file and rich release descriptions attached to Git tags on GitHub.

How text-to-CAD Tracks Versions

The project uses two primary mechanisms to manage public releases: a single-source-of-truth version file and GitHub's native release infrastructure.

The VERSION File

Located at the repository root, the VERSION file contains the current canonical version string (e.g., 0.3.13). This file serves as the single source of truth for the project's versioning scheme. When the maintainers cut a new release, the CI pipeline updates this file automatically, and the tag name matches the value stored within it.

GitHub Releases as the Changelog

Because the repository lacks a dedicated changelog document, GitHub Releases function as the authoritative source for human-readable release notes. Each Git tag creates a corresponding release page that displays the version number, release date, and a markdown-formatted description detailing new features, bug fixes, breaking changes, and migration instructions.

How to Access text-to-CAD Release Notes

You can view the complete release history through the web interface or programmatically via the GitHub API.

• Web Interface: Navigate to the Releases page and select any tag (e.g., v0.3.13) to view its associated notes.
• GitHub API: Fetch release metadata as JSON for integration into automated workflows or local tooling.

Automating Version Checks

Below are practical command-line snippets for retrieving the current version and fetching release notes programmatically.

Check the local version string stored in the repository:

cat VERSION

# → 0.3.13

List recent tags to identify available releases:

git tag --sort=-creatordate | head -n 5

# → v0.3.13

#   v0.3.12

#   v0.3.11

#   v0.3.10

#   v0.3.9

Fetch the release notes for the latest tag using the GitHub API with jq parsing:

LATEST_TAG=$(git describe --tags --abbrev=0)
curl -s "https://api.github.com/repos/earthtojake/text-to-cad/releases/tags/$LATEST_TAG" |
  jq -r '.body'

For a one-liner that displays both the current version and its corresponding release notes:

VERSION=$(cat VERSION)
curl -s "https://api.github.com/repos/earthtojake/text-to-cad/releases/tags/v$VERSION" |
  jq -r '"Version: \(.tag_name)\n\nRelease notes:\n\(.body)"'

Key Files Related to Releases

Understanding the release process requires familiarity with these specific files in the earthtojake/text-to-cad repository:

• VERSION – Located at the repository root, this file holds the canonical release version string used for tagging and CI validation.
• AGENTS.md – Contains repository-level workflow rules, including the specific release workflow and version handling procedures implemented by the maintainers.
• README.md – Provides high-level project context and references the release process for new contributors.

Summary

• text-to-CAD release notes reside exclusively on the GitHub Releases page, not in a committed changelog file.
• The VERSION file at the repository root provides the single source of truth for the current release number.
• Release automation is governed by workflow rules defined in AGENTS.md, which coordinates CI updates to the version file and tag creation.
• Developers can access historical changes via the web UI or programmatically through the GitHub API using the version string as the tag reference.

Frequently Asked Questions

Where is the CHANGELOG file for text-to-CAD?

There is no standalone CHANGELOG.md file in the repository. According to the source code structure, the project relies entirely on GitHub Releases to host human-readable release notes. Every version's changes are documented in the release description attached to its corresponding Git tag.

How do I programmatically fetch the latest text-to-CAD release notes?

Use the GitHub REST API endpoint for releases. First, read the VERSION file to get the canonical version number, then query https://api.github.com/repos/earthtojake/text-to-cad/releases/tags/v{VERSION}. The JSON response's body field contains the markdown-formatted release notes.

What triggers a new release of text-to-CAD?

As implemented in the repository's workflow rules defined in AGENTS.md, new releases are triggered through CI automation. When maintainers initiate a release, the pipeline updates the VERSION file, creates a matching Git tag, and publishes a GitHub Release with the provided description.

Does the VERSION file update automatically?

Yes. The VERSION file updates automatically via the CI pipeline whenever a new release is cut. This ensures the file remains synchronized with the latest Git tag, providing a consistent reference point for both automated systems and developers checking the local repository state.

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