From 3910e77a7a6ff747487b5ef484a67dbab5826f6a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Deluan=20Quint=C3=A3o?= Date: Sat, 21 Sep 2024 17:00:13 -0400 Subject: [PATCH] build(ci): change GitHub release notes (#3300) --- .github/workflows/pipeline.yml | 2 +- .goreleaser.yml | 42 ++++++++++++++++++++++++++++++++-- CONTRIBUTING.md | 17 +++++++------- 3 files changed, 50 insertions(+), 11 deletions(-) diff --git a/.github/workflows/pipeline.yml b/.github/workflows/pipeline.yml index 9eb338b87..faa06a7f7 100644 --- a/.github/workflows/pipeline.yml +++ b/.github/workflows/pipeline.yml @@ -24,7 +24,6 @@ jobs: uses: golangci/golangci-lint-action@v6 with: version: latest - github-token: ${{ secrets.GITHUB_TOKEN }} problem-matchers: true args: --timeout 2m @@ -99,6 +98,7 @@ jobs: name: js-bundle path: ui/build retention-days: 7 + i18n-lint: name: Lint i18n files runs-on: ubuntu-latest diff --git a/.goreleaser.yml b/.goreleaser.yml index 09d638067..000671390 100644 --- a/.goreleaser.yml +++ b/.goreleaser.yml @@ -126,9 +126,47 @@ snapshot: release: draft: true + mode: append + footer: | + **Full Changelog**: https://github.com/navidrome/navidrome/compare/{{ .PreviousTag }}...{{ .Tag }} + + ## Helping out + + This release is only possible thanks to the support of some **awesome people**! + + Want to be one of them? + You can [sponsor](https://github.com/sponsors/deluan), pay me a [Ko-fi](https://ko-fi.com/deluan) or [contribute with code](https://www.navidrome.org/docs/developers/). + + ## Where to go next? + + * Read installation instructions on our [website](https://www.navidrome.org/docs/installation/). + * Reach out on [Discord](https://discord.gg/xh7j7yF), [Reddit](https://www.reddit.com/r/navidrome/) and [Twitter](https://twitter.com/navidrome)! changelog: - # sort: asc + sort: asc + use: github filters: exclude: - - "^docs:" + - "^test:" + - Merge pull request + - Merge remote-tracking branch + - Merge branch + - go mod tidy + groups: + - title: "New Features" + regexp: '^.*?feat(\(.+\))??!?:.+$' + order: 100 + - title: "Security updates" + regexp: '^.*?sec(\(.+\))??!?:.+$' + order: 150 + - title: "Bug fixes" + regexp: '^.*?(fix|refactor)(\(.+\))??!?:.+$' + order: 200 + - title: "Documentation updates" + regexp: ^.*?docs?(\(.+\))??!?:.+$ + order: 400 + - title: "Build process updates" + regexp: ^.*?(build|ci)(\(.+\))??!?:.+$ + order: 400 + - title: Other work + order: 9999 diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6c08ea2c3..f2631f597 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -48,14 +48,15 @@ This improves the readability of the messages It can be one of the following: 1. **feat**: Addition of a new feature 2. **fix**: Bug fix -3. **docs**: Documentation Changes -4. **style**: Changes to styling -5. **refactor**: Refactoring of code -6. **perf**: Code that affects performance -7. **test**: Updating or improving the current tests -8. **build**: Changes to Build process -9. **revert**: Reverting to a previous commit -10. **chore** : updating grunt tasks etc +3. **sec**: Fixing security issues +4. **docs**: Documentation Changes +5. **style**: Changes to styling +6. **refactor**: Refactoring of code +7. **perf**: Code that affects performance +8. **test**: Updating or improving the current tests +9. **build**: Changes to Build process +10. **revert**: Reverting to a previous commit +11. **chore** : updating grunt tasks etc If there is a breaking change in your Pull Request, please add `BREAKING CHANGE` in the optional body section