Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/ISSUE_TEMPLATE/bug_report.yml
Original file line number Diff line number Diff line change
Expand Up @@ -10,8 +10,8 @@ body:
- type: input
id: version
attributes:
label: mcp-ariel-memory version
description: "Output of `pip show mcp-ariel-memory | grep Version`"
label: a-memory version
description: "Output of `pip show a-memory | grep Version`"
placeholder: "1.0.0"
validations:
required: true
Expand Down
10 changes: 6 additions & 4 deletions .github/release-drafter.yml
Original file line number Diff line number Diff line change
Expand Up @@ -5,9 +5,8 @@ template: |

$CHANGES

## Contributors

$CONTRIBUTORS
<!-- The body actually published comes from CHANGELOG.md — see
.github/workflows/release.yml. This draft is a working aid only. -->

categories:
- title: '🚀 Features'
Expand Down Expand Up @@ -36,7 +35,10 @@ categories:
labels:
- 'security'

change-template: '- $TITLE @$AUTHOR (#$NUMBER)'
# No `@$AUTHOR`: a commit author is a person, and this repository commits under
# a global git identity that is not meant to appear in release text. The
# `$CONTRIBUTORS` section was removed for the same reason.
change-template: '- $TITLE (#$NUMBER)'
change-title-escapes: '\<*_&'
version-resolver:
major:
Expand Down
23 changes: 22 additions & 1 deletion .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -27,11 +27,32 @@ jobs:
pip install build
python -m build

# The release body comes from CHANGELOG.md, never from generated notes.
# `generate_release_notes` built it out of PR titles and authors, which
# put a real committer identity into a public release ("@Cipher208 and
# Murat"). Notes written by hand in the CHANGELOG say what changed and
# why; a list of who touched it says neither. Failing here when the
# section is missing is deliberate — an empty body is better than a
# silently generated one, and the tag would be mis-built anyway.
- name: Take the release body from CHANGELOG.md
run: |
python - "${{ github.ref_name }}" > RELEASE_BODY.md <<'PY'
import re, sys
tag = sys.argv[1].lstrip("v")
text = open("CHANGELOG.md", encoding="utf-8").read()
m = re.search(rf"^## \[{re.escape(tag)}\][^\n]*\n(.*?)(?=^## \[|\Z)",
text, re.M | re.S)
if not m:
sys.exit(f"CHANGELOG.md has no '## [{tag}]' section — add one before tagging")
print(m.group(1).strip())
PY
test -s RELEASE_BODY.md

- name: Create GitHub Release
uses: softprops/action-gh-release@v2
with:
files: dist/*
generate_release_notes: true
body_path: RELEASE_BODY.md

- name: Publish to PyPI
env:
Expand Down
Loading
Loading