Commit graph

11 commits

Author SHA1 Message Date
4c332b32d3 feat: less repetitive entries for for prerelease changelogs
Right now we always show all new releasable commits since the last
_stable_ release.

If a project publishes multiple pre-releases in a row, they all repeat
the same lines with a few new additions.

On the other hand, when we cut a stable release, we do want to show all
changes since the last stable release, as we can not expect users to
read the changelog of pre-releases.

As a compromise, the code now looks at the type of release that is being
created, and decides based on that if we will look at STABLE..HEAD
(stable release) or LATEST..HEAD (pre-release).

Close #33
2024-08-30 19:40:05 +02:00
d5fd606577
chore: enable some more linters (#16) 2024-08-23 22:35:06 +02:00
5882a6bf2c refactor: move commit analyzing out of forge 2024-08-20 17:37:46 +02:00
f2a982d7a0 refactor: cleanup label handling 2024-08-20 17:37:46 +02:00
d8daad7623
refactor: Various cleanup (#11)
* refactor: interface for commit message analyzer

* refactor: interface for versioning strategy

* refactor(releasepr): rebuild pr description

Build PR description from scratch and parsed values instead of copying some of the AST to next description.
2024-08-08 19:01:44 +02:00
d1b9ae1908 feat: ensure labels exist in repo 2024-08-05 01:00:34 +02:00
6120821631 feat: tag releases on merged prs 2024-08-05 00:40:34 +02:00
fe871a0213 feat(releasepr): release PRs can be updated
- PR Description
- Read prefix+suffix from PR description and put into changelog
- Keep those overrides on PR description changes
- Add pending level to new PRs
2024-08-04 20:22:15 +02:00
e0b1e2221d feat: open pr 2024-08-03 03:00:36 +02:00
c7743e0a80 feat: push branch with changelog 2024-08-01 23:00:56 +02:00
8199918903 feat: parse existing release pr 2024-07-30 20:25:11 +02:00