GitHubFree GitHub release tool

GitHub Release Notes Generator

Paste merged pull requests or commits and get structured release notes, a changelog entry, and a GitHub release body without connecting a token.

Current release

glink/glink v1.4.0 release notes

glink/glink v1.4.0 is ready for developers, with updates around prevent duplicate notification emails after deploy, speed up roadmap filters for shipped work and rename glink_api_token to glink_token.

GitHub release body

glink/glink v1.4.0 release notes

glink/glink v1.4.0 is ready for developers, with updates around prevent duplicate notification emails after deploy, speed up roadmap filters for shipped work and rename glink_api_token to glink_token.
## Improvements

- Speed up roadmap filters for shipped work. (#152)

## Fixes

- Prevent duplicate notification emails after deploy. (#149, @ivan)

## Breaking changes

- Rename GLINK_API_TOKEN to GLINK_TOKEN. (#160)

## Maintenance

- Add public changelog embeds for release pages. (#148, @mira)
- Add API examples for changelog widgets. (#155)

## Upgrade notes
Review the breaking changes before upgrading and update any affected configuration, environment variables, or integrations.

Features

0

New capabilities and shipped product surface.

Improvements

1

Performance, polish, and workflow upgrades.

Fixes

1

Bugs, regressions, and reliability repairs.

Breaking changes

1

Migration notes users need before upgrading.

Maintenance

2

Docs, dependencies, chores, and internal cleanup.

Changelog entry

Copy into CHANGELOG.md

## v1.4.0
glink/glink v1.4.0 is ready for developers, with updates around prevent duplicate notification emails after deploy, speed up roadmap filters for shipped work and rename glink_api_token to glink_token.
### Improvements

- Speed up roadmap filters for shipped work. (#152)

### Fixes

- Prevent duplicate notification emails after deploy. (#149, @ivan)

### Breaking changes

- Rename GLINK_API_TOKEN to GLINK_TOKEN. (#160)

### Maintenance

- Add public changelog embeds for release pages. (#148, @mira)
- Add API examples for changelog widgets. (#155)

### Upgrade notes
Review the breaking changes before upgrading and update any affected configuration, environment variables, or integrations.

Release notes sections

What changed

Features

No items detected for this section.

Improvements

  • Speed up roadmap filters for shipped work. (#152)

Fixes

  • Prevent duplicate notification emails after deploy. (#149, @ivan)

Breaking changes

  • Rename GLINK_API_TOKEN to GLINK_TOKEN. (#160)

Maintenance

  • Add public changelog embeds for release pages. (#148, @mira)
  • Add API examples for changelog widgets. (#155)

Publish releases where users can follow them.

Glink turns release notes into a public changelog, roadmap context, feedback loop, and product timeline.

Publish in Glink

Does this connect to GitHub?

No. This GitHub release notes generator is client-only. Paste merged pull requests or commits from GitHub and it formats them in your browser without an API token.

What should I paste into the generator?

Paste merged pull request titles, commit messages, issue titles, conventional commits, or a rough list of changes for the release.

Can I use the output in a GitHub release?

Yes. Copy the GitHub release body directly into a GitHub release, or export the full Markdown draft with release notes and a changelog entry.