Merge branch 'music-assistant:dev' into dev

Author: anatosun

.github/release-drafter.yml

@@ -1,7 +1,11 @@
 change-template: '- $TITLE (by @$AUTHOR in #$NUMBER)'
-prerelease: true
-prerelease-identifier: 'b'
-include-pre-releases: true
+
+# Note: prerelease flag is set dynamically by the workflow based on channel
+# This config is used for all release channels (stable, beta, nightly)
+
+# Filter releases by commitish (branch) to only show releases from the same branch
+# This allows us to have separate release notes for stable/beta/nightly channels
+filter-by-commitish: true
 
 # Exclude bots from contributors list
 exclude-contributors:

.github/workflows/RELEASE_NOTES_GENERATION.md

@@ -0,0 +1,205 @@
+# Release Notes Generation - Channel-Specific Behavior
+
+## Overview
+
+The release workflow generates release notes **specific to each channel** by leveraging Release Drafter's `filter-by-commitish` feature. This ensures that:
+
+- **Stable** releases only show commits from the `stable` branch
+- **Beta** releases only show commits from the `dev` branch since the last beta
+- **Nightly** releases only show commits from the `dev` branch since the last nightly
+
+The workflow uses your **Release Drafter configuration** (`.github/release-drafter.yml`) for label-based categorization and formatting.
+
+## How It Works
+
+### 1. Filter by Branch (commitish)
+
+The `.github/release-drafter.yml` file includes:
+
+```yaml
+filter-by-commitish: true
+```
+
+This tells Release Drafter to only consider releases that have the same `target_commitish` (branch) when calculating the commit range. Combined with setting the `commitish` parameter to the appropriate branch:
+
+- **Stable releases**: Use `commitish: stable` → Only sees releases created from `stable` branch
+- **Beta releases**: Use `commitish: dev` → Only sees releases created from `dev` branch
+- **Nightly releases**: Use `commitish: dev` → Only sees releases created from `dev` branch
+
+### 2. Previous Release Detection
+
+The workflow also manually identifies the previous release for context headers using tag patterns:
+
+#### Stable Channel
+- **Pattern**: `^[0-9]+\.[0-9]+\.[0-9]+$` (e.g., `2.1.0`, `2.0.5`)
+- **Branch**: `stable`
+- **Finds**: Latest stable release (no suffix)
+
+#### Beta Channel
+- **Pattern**: `^[0-9]+\.[0-9]+\.[0-9]+\.b[0-9]+$` (e.g., `2.1.0.b1`, `2.1.0.b2`)
+- **Branch**: `dev`
+- **Finds**: Latest beta release (`.bN` suffix)
+
+#### Nightly Channel
+- **Pattern**: `^[0-9]+\.[0-9]+\.[0-9]+\.dev[0-9]+$` (e.g., `2.1.0.dev20251023`)
+- **Branch**: `dev`
+- **Finds**: Latest nightly release (`.devYYYYMMDD` suffix)
+
+### 3. Release Notes Generation
+
+Release Drafter automatically:
+
+1. **Finds commit range**: Determines commits between the previous release (same branch) and HEAD
+2. **Extracts PRs**: Identifies all merged pull requests in that range
+3. **Categorizes by labels**: Applies the category rules from `.github/release-drafter.yml`:
+   - ⚠ Breaking Changes (`breaking-change` label)
+   - 🚀 New Providers (`new-provider` label)
+   - 🚀 Features and enhancements (`feature`, `enhancement`, `new-feature` labels)
+   - 🐛 Bugfixes (`bugfix` label)
+   - 🧰 Maintenance (`ci`, `documentation`, `maintenance`, `dependencies` labels)
+4. **Lists contributors**: Adds all unique contributors from the PRs
+
+The workflow then enhances these notes by:
+- Adding a context header showing the previous release
+- Extracting and appending frontend changes from frontend update PRs
+- Merging and deduplicating contributors from both server and frontend
+
+### 4. What This Means
+
+#### ✅ Stable Release Notes
+- Include **only commits since the last stable release**
+- **Do NOT include** beta or nightly commits that happened in between
+- Example: `2.0.5` → `2.1.0` only shows stable branch commits
+
+#### ✅ Beta Release Notes
+- Include **only commits since the last beta release**
+- **Do NOT include** nightly commits
+- **Do NOT include** stable commits from stable branch
+- Example: `2.1.0.b2` → `2.1.0.b3` only shows dev branch commits since b2
+
+#### ✅ Nightly Release Notes
+- Include **only commits since the last nightly release**
+- **Do NOT include** beta or stable releases in between
+- Example: `2.1.0.dev20251022` → `2.1.0.dev20251023` only shows dev branch commits since yesterday
+
+## Release Drafter Configuration
+
+✅ The workflow **uses Release Drafter natively** with the following key configuration:
+
+```yaml
+# .github/release-drafter.yml
+filter-by-commitish: true  # Only consider releases from the same branch
+```
+
+This configuration, combined with setting the appropriate `commitish` parameter when calling Release Drafter, ensures:
+- **No temporary hiding of releases** (avoids updating publish dates)
+- **Native Release Drafter filtering** (robust and reliable)
+- **Branch-based separation** (stable vs dev commits are naturally separated)
+
+The workflow also uses your existing configuration for:
+- Category definitions (labels → section headers)
+- Category titles and emoji
+- Excluded contributors (bots)
+- PR title format
+
+## Example Release Notes Format
+
+```markdown
+## 📦 Beta Release
+
+_Changes since [2.1.0.b1](https://github.com/music-assistant/server/releases/tag/2.1.0.b1)_
+
+### ⚠ Breaking Changes
+
+- Major API refactoring (by @contributor1 in #123)
+
+### 🚀 Features and enhancements
+
+- Add new audio processor (by @contributor2 in #124)
+- Improve queue management (by @contributor3 in #125)
+
+### 🐛 Bugfixes
+
+- Fix playback issue (by @contributor1 in #126)
+
+### 🧰 Maintenance and dependency bumps
+
+- Update dependencies (by @dependabot in #127)
+- Improve CI pipeline (by @contributor2 in #128)
+
+## :bow: Thanks to our contributors
+
+Special thanks to the following contributors who helped with this release:
+
+@contributor1, @contributor2, @contributor3
+```
+
+## Testing
+
+To verify channel-specific release notes:
+
+1. **Create a beta release** after a stable release:
+   ```bash
+   # Should only show commits on dev branch since last beta
+   # Should NOT include stable branch commits
+   ```
+
+2. **Create a nightly release** after a beta release:
+   ```bash
+   # Should only show commits since yesterday's nightly
+   # Should NOT include beta release notes
+   ```
+
+3. **Create a stable release** after multiple betas:
+   ```bash
+   # Should only show commits on stable branch since last stable
+   # Should NOT include any beta or nightly commits
+   ```
+
+## Verification Commands
+
+```bash
+# Check what will be in next stable release
+git log $(git tag | grep -E '^[0-9]+\.[0-9]+\.[0-9]+$' | sort -V | tail -1)..stable --oneline
+
+# Check what will be in next beta release
+git log $(git tag | grep -E '^[0-9]+\.[0-9]+\.[0-9]+\.b[0-9]+$' | sort -V | tail -1)..dev --oneline
+
+# Check what will be in next nightly release
+git log $(git tag | grep -E '^[0-9]+\.[0-9]+\.[0-9]+\.dev[0-9]+$' | sort -V | tail -1)..dev --oneline
+```
+
+## Testing
+
+To verify channel-specific release notes:
+
+1. **Create a beta release** after a stable release:
+   ```bash
+   # Should only show commits on dev branch since last beta
+   # Should NOT include stable branch commits
+   ```
+
+2. **Create a nightly release** after a beta release:
+   ```bash
+   # Should only show commits since yesterday's nightly
+   # Should NOT include beta release notes
+   ```
+
+3. **Create a stable release** after multiple betas:
+   ```bash
+   # Should only show commits on stable branch since last stable
+   # Should NOT include any beta or nightly commits
+   ```
+
+## Verification Commands
+
+```bash
+# Check what will be in next stable release
+git log $(git tag | grep -E '^[0-9]+\.[0-9]+\.[0-9]+$' | sort -V | tail -1)..stable --oneline
+
+# Check what will be in next beta release
+git log $(git tag | grep -E '^[0-9]+\.[0-9]+\.[0-9]+\.b[0-9]+$' | sort -V | tail -1)..dev --oneline
+
+# Check what will be in next nightly release
+git log $(git tag | grep -E '^[0-9]+\.[0-9]+\.[0-9]+\.dev[0-9]+$' | sort -V | tail -1)..dev --oneline
+```