How to manage tags when using the independent strategy.

I'm looking into monorepos and Lerna as an option for some upcoming work and running into a bit of a snag when it comes to using the independent option for managing packages and deployments with --conventional-commits. I've looked at a few open source examples that are using Lerna with the independent option (i.e. materia-ui) and noticed that their tagging, releases, and changelogs are all being grouped under a top level (vX.x.x) tag structure rather than per package (package-name@X.x.x). Is this something that Lerna supports and in the documentation somewhere?

Additionally is CI/CD options for managing deployments still not a recommended or supported option with Lerna? I'm looking for something similar to semantic-release functionality and support but not finding much guidance in your documentation around this.

{
  "version": "independent",
  "npmClient": "yarn",
  "packages": ["packages/*"],
  "useWorkspaces": true,
  "command": {
    "publish": {
      "allowBranch": [
        "master",
        "next",
        "alpha",
        "beta",
        "[0-9].x",
        "[0-9][0-9].x",
        "[0-9][0-9][0-9].x",
        "[0-9][0-9][0-9][0-9].x"
      ],
      "message": "chore: publish package",
      "ignoreChanges": ["*.md", "*.mdx", "*.json", "docs", "package.json"],
      "conventionalCommits": true
    },
    "init": {
      "exact": true
    }
  }
}

Context

Looking to be able automate our monorepo package deployments via Github Actions rather than manually to minimize error. Also looking to support patching a previous major release so we can support multiple majors for our team.

Your Environment

Start with the linked lerna.json configuration and compare the referenced Material UI tags, releases, and changelog. Review the documentation for independent versioning, conventional commits, and publish workflows, then document whether per-package tags and GitHub Actions deployments are supported, including what a completed guidance update should cover.