<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Conventional Changelog on My learning and diary</title>
    <link>https://jackliusr.github.io/tags/conventional-changelog/</link>
    <description>Recent content in Conventional Changelog on My learning and diary</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 09 Jun 2026 10:00:00 +0800</lastBuildDate><atom:link href="https://jackliusr.github.io/tags/conventional-changelog/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>From Conventional Commits to LLM-Generated Release Notes</title>
      <link>https://jackliusr.github.io/posts/2026/06/from-conventional-commits-to-llm-generated-release-notes/</link>
      <pubDate>Tue, 09 Jun 2026 10:00:00 +0800</pubDate>
      
      <guid>https://jackliusr.github.io/posts/2026/06/from-conventional-commits-to-llm-generated-release-notes/</guid>
      <description>Introduction For several years, I adopted Conventional Commits across my software projects. The premise was straightforward: write commit messages in a structured, machine-readable format, then leverage tooling to generate changelogs and release notes automatically.
 For example:
 feat: add user login fix: resolve payment retry issue docs: update API usage guide   This approach served me well. Tools like Conventional Changelog could parse commit history and produce structured release notes with minimal manual effort.</description>
    </item>
    
  </channel>
</rss>
