Refactor release workflow to include version bump type as input

Author: hhfrancois

.github/workflows/release.yml

@@ -1,28 +1,44 @@
 name: Create Tag/Release
-run-name: ${{ github.actor }} run build on ${{ github.repository }}
+run-name: ${{ github.actor }} release ${{ inputs.bump }} on ${{ github.repository }}
+
 on:
   workflow_dispatch:
+    inputs:
+      bump:
+        description: "Version bump type"
+        required: true
+        default: patch
+        type: choice
+        options:
+          - patch
+          - minor
+          - major
+
+permissions:
+  contents: write
+
 jobs:
-  create-release:
+  release:
+    name: Bump, tag and release
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - name: Checkout code
+        uses: actions/checkout@v4
         with:
-          token: ${{ secrets.PAT_TOKEN }}
-      - uses: actions/setup-node@v4
+          fetch-depth: 0
+          token: ${{ secrets.PAT_TOKEN }} # PAT so the pushed tag triggers tag.yml (publish)
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
         with:
-          node-version: '20'
-      - run: git config user.name "$GITHUB_ACTOR"
-      - run: git config user.email ""
-      - name: Version, prepare next release notes, and push
+          node-version: "20"
+
+      - name: Install, build and smoke test
         run: |
-          npm version patch
-          CURRENT_VERSION=$(node -p "require('./package.json').version")
-          IFS='.' read -r MAJOR MINOR PATCH <<< "$CURRENT_VERSION"
-          NEXT_VERSION="$MAJOR.$MINOR.$((PATCH + 1))"
-          sed -i "s/^# Release Notes$/# Release Notes\n\n## $NEXT_VERSION\n\n---/" RELEASE_NOTES.md
-          git add RELEASE_NOTES.md
-          git commit --amend --no-edit
-          git push --all
-          git push --tags
+          npm ci
+          npm run build
+          npm test
 
+      - uses: softwarity/release-flow@v1
+        with:
+          bump: ${{ inputs.bump }} # the value picked in the dropdown

README.md

@@ -33,6 +33,7 @@ An Angular directive that creates a [Material Design 3 split button](https://m3.
 - **Material Design 3 Compliant** - Follows M3 button specifications
 - **5 Button Variants** - Text, Filled, Tonal, Outlined, Elevated
 - **Responsive to Theme** - Automatically adapts to light/dark color schemes
+- **Toolbar-aware** - Text & outlined variants auto-adapt their label color inside a `mat-toolbar`
 - **MatMenu Integration** - Works seamlessly with Angular Material's menu component
 - **Material 3 Ready** - Uses M3 design tokens for theming (`--mat-sys-*`)
 - **Standalone Directive** - Easy to import in any Angular 21+ application
@@ -151,6 +152,10 @@ The `overrides` mixin accepts a map of tokens to customize the appearance:
 | `elevated-container-color` | `var(--mat-sys-surface-container-low)` | Container color for elevated variant |
 | `elevated-label-color` | `var(--mat-sys-primary)` | Label color for elevated variant |
 
+### Adapting to the surrounding container
+
+The transparent variants (`text` and `outlined`) inherit `--mat-toolbar-container-text-color`, so their label and chevron automatically match the text color of a surrounding `mat-toolbar` — just like a real `matButton`. Outside a toolbar they fall back to `var(--mat-sys-primary)`. The container variants (`filled`, `tonal`, `elevated`) keep their own label color over their own background. You can override any of this with the tokens above.
+
 ### Examples
 
 ```scss

RELEASE_NOTES.md

@@ -1,6 +1,32 @@
 # Release Notes
 
-## 1.0.2
+## NEXT RELEASE
+
+### Fixes
+- **Theming on Angular Material 17+**: migrated every button design token from the
+  legacy `--mdc-*-button-*` names to the current `--mat-button-*` names — label and
+  container colors, outline color, container shape (border-radius) and elevation
+  shadow. Material no longer emits the `--mdc-*` tokens, so the directive previously
+  fell through to its `--mat-sys-*` fallbacks and ignored any button-level
+  customization coming from the Angular Material theme (e.g. `mat.button-overrides(...)`).
+  The `--split-button-*` overrides and `--mat-sys-*` defaults are unaffected.
+- **Auto-adapt inside a `mat-toolbar`**: the transparent variants (text, outlined)
+  now fall back to `--mat-toolbar-container-text-color`, so their label and chevron
+  pick up the toolbar's text color automatically — matching how a real `matButton`
+  behaves. The container variants (filled, tonal, elevated) are unchanged (they keep
+  their own label color over their own background).
+
+### Docs
+- README and demo documentation now describe the toolbar auto-adaptation behavior.
+- Demo playground gains a contrasted `mat-toolbar` example (the split-button's label
+  follows the toolbar text color) and carousel pickers for the `variant` and Material
+  `palette` selectors.
+
+### Chore
+- Updated the dev/build toolchain to patched releases (Angular 21.2.x, Angular CDK/Material
+  21.2.14) and pinned `undici`/`@babel/core` via npm `overrides`, clearing all high/moderate
+  `npm audit` advisories. These are devDependencies only — the published package is unaffected
+  (it ships nothing but `tslib` at runtime).
 
 ---
 
@@ -67,4 +93,3 @@
 - Includes hidden-trigger utility styles
 
 ---
-

angular.json

@@ -110,5 +110,8 @@
     "@schematics/angular:resolver": {
       "typeSeparator": "."
     }
+  },
+  "cli": {
+    "analytics": false
   }
 }