Skip to content

chore(tidy3d-client): build release notes from changelog#3365

Draft
marcorudolphflex wants to merge 1 commit into
flexcompute:developfrom
marcorudolphflex:marco/changelog-release-notes
Draft

chore(tidy3d-client): build release notes from changelog#3365
marcorudolphflex wants to merge 1 commit into
flexcompute:developfrom
marcorudolphflex:marco/changelog-release-notes

Conversation

@marcorudolphflex
Copy link
Copy Markdown
Contributor

@marcorudolphflex marcorudolphflex commented Apr 23, 2026

Summary

Use the tagged CHANGELOG.md release section as the GitHub release body instead of GitHub autogenerated release notes.

Why

The current release workflow on latest still lets GitHub infer the compare range and note content. That can publish duplicated or misleading notes when GitHub chooses the wrong baseline.

This change makes the GitHub release page match the curated changelog content for the tagged release.

Behavior

  • publish the matching release section from CHANGELOG.md as ## What's Changed
  • use the changelog compare link when present
  • fall back to a compare link derived from adjacent release headings for older changelog entries that do not yet have a footer link

Validation

  • python3 -m py_compile scripts/build_github_release_notes.py
  • python3 scripts/build_github_release_notes.py --tag v2.9.2 --output /tmp/tidy3d-latest-release-notes-test.md
  • YAML parse of .github/workflows/tidy3d-python-client-release.yml

@marcorudolphflex marcorudolphflex changed the title ci: build tidy3d release notes from changelog chore(tidy3d-client): build release notes from changelog Apr 23, 2026
@marcorudolphflex marcorudolphflex force-pushed the marco/changelog-release-notes branch 3 times, most recently from 63bae80 to f96b7d3 Compare April 23, 2026 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant