{"slug": "changelog-docs-follow-up-after-four-months", "title": "Changelog Docs: Follow-Up After Four Months", "summary": "A developer's four-month follow-up test of changelog-driven documentation on the Trongate PHP framework found that the project's AI assistant, Grady, updated the changelog for all 17 releases since June 2026 without apparent human intervention, though its entries default to wordy bullet paragraphs rather than concise points. The author also reported that a deliberately minimal README written in April still worked when retested on October 7, 2026, while the narrative docs repo had not been updated since August 25, 2026, a one-month lag behind the latest September 27 release.", "body_md": "In a [previous post](https://dev.to/alexiskypridemos/changelog-vs-narrative-documentation-a-real-world-test-1kck), I tested a changelog-driven approach to documentation using a real open source project, the [Trongate PHP framework](https://trongate.io).\n\nThe open questions then were:\n\nAnswering those questions:\n\nIt seems like the framework maintainers have hit on an automated workflow that works for them. Their AI assistant, [Grady](https://github.com/grady-trongate), has updated the changelog with each of the 17 releases since I published the previous article on June 9th, 2026, without apparent human intervention. \n\nThe only exceptions were a couple of releases in early to mid July, for which I [updated the changelog manually](https://github.com/trongate/trongate-framework/pull/246).\n\nA writer's gripe: while clearly timely and hopefully effortless for the maintainers, the AI is wordy. Whereas I pictured the changelog as a series of bullet *points* of about a line or so, the AI defaults to bullet *paragraphs*. \n\nI realized \"Will users find it useful?\" was an ambitious question, and I have no good way to measure to that. I'm open to suggestions.\n\nI searched for \"changelog\" on [Trongate's forums](https://trongate.io/forums/search_results/Sd29L6y2DsykQ5bY), but none of the results were a user reaction.\n\nThe latest framework release was on [September 27, 2026](https://github.com/trongate/trongate-framework/pull/275), but the docs repo has not been updated since [August 25, 2026](https://github.com/trongate/trongate-docs/commit/99716a16c75e1ad614cd56bc39bc8865bf9578a3).\n\nA one-month documentation lag for an open source project is, I would argue, hardly mission critical. However, I think this goes toward proving my point: long, narrative documentation does not lend itself to being updated at the typical rate of change of most software projects.\n\nThis wasn't a question four months ago, but after 17 releases, I wondered if the [README I wrote in April](https://github.com/trongate/trongate-framework/commit/22baa63c3234148302b5af3c8377bd8b556a0d94), and which hasn't been updated since, still works.\n\nIt does.\n\nI tested it again today, October 7, 2026, and the instructions still work, which, in my humble opinion, proves one of my other points: you want to keep the documentation primitive and deliberately **not all-inclusive** so that it remains reasonably accurate and future-proof, enduring multiple future releases with **zero maintenance**.\n\nFor example, navigating to the local Trongate installation's index page is a different experience today than it was in June. However, the instructions don't reference that page. Instead, they say to go to `http://localhost/trongate/demo`. A cheap writer's trick, but it works.", "url": "https://wpnews.pro/news/changelog-docs-follow-up-after-four-months", "canonical_source": "https://dev.to/alexiskypridemos/changelog-docs-follow-up-after-four-months-1178", "published_at": "2026-10-07 11:12:57+00:00", "updated_at": "2026-10-07 11:17:17.335334+00:00", "lang": "en", "topics": ["ai-tools", "developer-tools", "generative-ai"], "entities": ["Trongate", "Grady", "Trongate PHP framework", "GitHub"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/changelog-docs-follow-up-after-four-months", "markdown": "https://wpnews.pro/news/changelog-docs-follow-up-after-four-months.md", "text": "https://wpnews.pro/news/changelog-docs-follow-up-after-four-months.txt", "jsonld": "https://wpnews.pro/news/changelog-docs-follow-up-after-four-months.jsonld"}}