Library release automation MVP

[validbeck]

Pull Request Description

What and why?

Adds triggers on validmind/validmind-library so stable semver releases dispatch the library release-notes workflow after pilot.

notify-library-release-notes.yaml

• Listens on v* tag push when RELEASE_AUTOMATION=true
• Skips prerelease suffixes (-rc, -alpha, -beta)
• Dispatches library-release-notes to validmind/release-notes with the pushed tag in client-payload
• Patch and feature classification happens in release-notes discovery (release_type_hint from semver bump)

How to test

n/a — Automatic release generation workflows will run when flags are turned on.

What needs special review?

n/a

Dependencies, breaking changes, and deployment notes

Related epic PRs

1. release-notes
2. documentation
3. skills
4. installation

Release notes

n/a

Checklist

• What and why
• Screenshots or videos (Frontend)
• How to test
• What needs special review
• Dependencies, breaking changes, and deployment notes
• Labels applied
• PR linked to Shortcut
• Unit tests added (Backend)
• Tested locally
• Documentation updated (if required)

[github-actions]

PR Summary

This pull request introduces a new GitHub Actions workflow titled "Notify library release notes." The workflow is designed to automatically trigger on push events that include tags matching the pattern v*. Its primary function is to determine if the tag represents a pre-release (e.g., containing -rc, -alpha, or -beta) and, if not, dispatch an event to a separate repository to process release notes.

Key functional changes include:

• A job that runs only if the RELEASE_AUTOMATION variable is set to true.
• A bash script step that filters out pre-release tags by checking for substrings such as rc, alpha, or beta in the tag name. If a pre-release tag is detected, the subsequent steps are skipped.
• A conditional step that uses the peter-evans/repository-dispatch action to send a payload containing the tag to the release-notes repository, effectively notifying it of a new release.

Overall, the workflow aims to streamline the release process by automating the release notes notification for valid release tags.

Test Suggestions

• Test that the workflow triggers on a valid release tag (e.g., v1.0.0) and dispatches the repository event correctly.
• Test with a pre-release tag (e.g., v1.0.0-beta) to ensure the workflow properly skips the release notes dispatch.
• Verify that the workflow does not execute if the RELEASE_AUTOMATION variable is not set to 'true'.
• Simulate failure scenarios (e.g., missing secrets or incorrect tag format) to verify error handling in the workflow.