fix(ci): use github auto-generated release notes

Author: dmirtillo

.github/workflows/docker-image.yml

@@ -97,12 +97,7 @@ jobs:
           docker push $DOCKERHUB_REPO:latest
           docker push $DOCKERHUB_REPO:$TAG_NAME
 
-      - name: Extract Release Notes
-        id: extract_notes
-        run: |
-          awk '/^## \[/ { if (p) exit; p=1; next } p' CHANGELOG.md > release_notes.md
-
       - name: Create GitHub Release
         uses: softprops/action-gh-release@v2
         with:
-          body_path: release_notes.md
+          generate_release_notes: true

openspec/changes/archive/2026-02-28-github-releases/specs/ci-publishing/spec.md

@@ -2,10 +2,10 @@
 
 ### Requirement: Automated GitHub Releases
 The pipeline SHALL automatically create a GitHub Release when a `v*.*.*` semantic version tag is pushed.
-- The release MUST include release notes extracted from the `CHANGELOG.md` corresponding to the latest release block.
+- The release MUST automatically generate release notes containing the commit messages/PRs since the last tag.
 - The release MUST be created using the `GITHUB_TOKEN` provided by the Actions runner.
 
 #### Scenario: Creating a release on tag push
 - **WHEN** a semantic version tag (e.g., `v1.0.0`) is pushed and tests pass
 - **THEN** a GitHub Release is created for the tag
-- **THEN** the release body contains the relevant changelog notes
+- **THEN** the release body contains the auto-generated commit log

openspec/specs/ci-publishing/spec.md

@@ -74,10 +74,10 @@ The CI pipeline SHALL include automated workflows that check for updates to crit
 
 ### Requirement: Automated GitHub Releases
 The pipeline SHALL automatically create a GitHub Release when a `v*.*.*` semantic version tag is pushed.
-- The release MUST include release notes extracted from the `CHANGELOG.md` corresponding to the latest release block.
+- The release MUST automatically generate release notes containing the commit messages/PRs since the last tag.
 - The release MUST be created using the `GITHUB_TOKEN` provided by the Actions runner.
 
 #### Scenario: Creating a release on tag push
 - **WHEN** a semantic version tag (e.g., `v1.0.0`) is pushed and tests pass
 - **THEN** a GitHub Release is created for the tag
-- **THEN** the release body contains the relevant changelog notes
+- **THEN** the release body contains the auto-generated commit log