I generated the CHANGELOG doc which summarizes all previous releases.

Instead of using release-drafter, this introduces 3 workflows:

labeler.yml

A reusable workflow that employs actions/labeler to auto manage certain labels based on branch name and changed files. It also has a step to add labels based on PR title (using gh-cli). This workflow is designed to be a replacement of the auto-labeler behavior in release-drafter.

The config for actions/labeler resides in this repo under .github/labeler.yml.

unreleased-summary.yml

A reusable workflow that will summarize unreleased changes in the run's summary (GITHUB_STEP_SUMMARY).

tag-release.yml

A manually-triggered workflow that invokes the tag-release.nu script (primarily designed to be executed in CI).

This tag-release workflow will take input:

• component (optional): The version component to bump. Supported values are

  cpp-linter/.github/workflows/tag-release.yml

  Lines 15 to 19 in 22a1041

  	options:
  	- auto
  	- patch
  	- minor
  	- major

  If auto is selected (the default value), the version will be bumped according to the unreleased changes (via git-cliff bump policy in .github/cliff.toml). Observe the step summary from the unreleased-summary.yml workflow because it uses the auto version bump feature.

A script that will

1. Generate Release notes (from unreleased changes).
2. (Re)generate the CHANGELOG.md in repo root and push any changes
3. Create a GitHub release, which in turn creates a git tag on the default branch  
4. Move any major tags (eg. v2) that correspond with the new release's tag.        
   This step does nothing if no major tag exists.

This script is designed to be run in CI or locally.
Either way, this script will abort if the current branch is not 'main'.

The following tools are used and must be installed:

- git (https://git-scm.com/)
- uv (https://docs.astral.sh/uv/) used to install/run git-cliff.
  See .github/requirements.txt for the pinned version of git-cliff.
- gh-cli (https://cli.github.com/)

Supported component parameter values are:

- auto (relies on git-cliff to determine the next version)
- patch
- minor
- major

If no component is given, then auto is used.

Usage:
  > tag-release.nu (component)

Flags:
  -h, --help: Display the help message for this command

Parameters:
  component <string>: The version component to bump. (optional)