release-notes

When tasked to generate release notes for a given version, your goal is to produce good-quality release notes focused on the user of Agent Stack. You don't need to provide a list of changed tickets or merged PRs; your goal is to provide human-readable release notes focused on the impact on the user.

Scope of the release

The user generally provides a version tag for which they want to generate release notes. For example, they might tell you something like "Generate release notes for release-v0.5.0". Your first task is to figure out what the scope of the release is. The scope is basically a list of all merged PRs; once you have this list, you can proceed to the next steps.

How to figure out the scope of the release

The user tells you for which version they want to generate the release notes, e.g., release-v0.5.0. Your next step is to figure out what the start commit in the git history is, and then you compare that with the head of the given release, e.g., release-v0.5.0.

The start commit is the latest stable version of the Agent Stack.

You can easily find the last release commit by looking at the install branch in i-am-bee/agentstack and checking the install.sh script in the root of the repo, which contains the LATEST_STABLE_AGENTSTACK_VERSION variable.

For example, you can do something like this:

curl -s https://raw.githubusercontent.com/i-am-bee/agentstack/install/install.sh | grep 'LATEST_STABLE_AGENTSTACK_VERSION=' | cut -d'=' -f2