Enable v1.0.0 release with enhanced version workflow

[Copilot]

Description

Release workflow couldn't accept explicit version numbers for v1.0.0 deployment. This PR enhances the release workflow to support specific version numbers while maintaining backward compatibility with semantic versioning keywords.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Workflow/CI improvement
• Dependency update

Related Issue

Fixes #(issue number)

Changes Made

release.yml - Support explicit version numbers

• Enhanced version parsing to accept 1.0.0 or v1.0.0 in addition to major/minor/patch
• Regex pattern: ^v?[0-9]+\.[0-9]+\.[0-9]+$ validates and strips prefix
• Maintains backward compatibility with semantic bump keywords

README.md - Release documentation

• Added release instructions for v1.0.0 deployment
• Documented both automatic and manual release workflows
• Explained version input options (specific versions or semantic keywords)

CHANGELOG.md - Version workflow enhancement

• Documented release workflow enhancement in [Unreleased] section
• Added entry for specific version number support

Changelog

• I have updated CHANGELOG.md under the [Unreleased] section
• No changelog update needed (documentation/CI only)

Testing

• All existing tests pass
• I have added tests for my changes (if applicable)
• I have tested the changes locally
• Workflow checks pass

Validation performed:

• YAML syntax validation (all workflows)
• Version parsing tested: 1.0.0, v1.0.0, major, minor, patch
• Verified regex pattern matches semantic version format
• CodeQL security scan: 0 alerts

Documentation

• I have updated relevant documentation
• No documentation updates needed

Security

• My changes don't introduce security vulnerabilities
• I have reviewed security scan results
• No security concerns

Security review:

• Version input properly validated with regex pattern
• No code injection vectors in version parsing
• No secrets exposed

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code where necessary
• My changes generate no new warnings
• Any dependent changes have been merged and published

Additional Notes

Deploy v1.0.0: Actions → Release and Marketplace → Run workflow → Enter 1.0.0 → Run

The release workflow now supports:

• Specific versions: 1.0.0, v1.0.0, 2.5.3
• Semantic keywords: major, minor, patch

Original prompt

Ensure README.md is updated to reflect the most recent changes. Review current code base and update as needed to create a MVP or finished product and if possible update the release workflow to allow me to deploy v1 or v1.0.0 after all the changes have been completed.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[thoughtparametersllc]

@copilot Remove those missing inputs as I intentionally removed them

[Copilot]

@copilot Remove those missing inputs as I intentionally removed them

Reverted the addition of those inputs (generate-badges, update-readme, readme-path, badge-style) and removed the README update step from action.yml. Badge generation now runs unconditionally as it did originally. The release workflow enhancement for specific version numbers is retained. Commit: f6d8bb5

[thoughtparametersllc]

Good.

[Copilot]

Pull Request Overview

This PR enhances the release workflow to support explicit version number input (e.g., 1.0.0 or v1.0.0) while maintaining backward compatibility with semantic versioning keywords (major, minor, patch). This enables direct deployment of v1.0.0 through the GitHub Actions interface.

Key Changes:

• Modified version parsing logic in the release workflow to accept both explicit semantic versions and bump keywords
• Added comprehensive release documentation to README.md explaining both automatic and manual release workflows
• Updated CHANGELOG.md to document the new explicit version number support

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
.github/workflows/release.yml	Enhanced version determination logic with regex validation to accept explicit versions (e.g., 1.0.0, v1.0.0) in addition to semantic bump keywords
README.md	Added "Releasing" section documenting both automatic and manual release workflows with examples of version input formats
CHANGELOG.md	Documented the release workflow enhancement under [Unreleased] in both "Added" and "Changed" sections

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

When a specific version is provided, there's no validation to prevent version downgrades or duplicate versions. Consider adding a check to ensure the specified version is greater than the latest tag and doesn't already exist:

# After line 128, add validation
if git tag -l "$NEW_VERSION" | grep -q "$NEW_VERSION"; then
  echo "Error: Version $NEW_VERSION already exists as a tag"
  exit 1
fi

# Also verify version is greater than current
if [[ "$NEW_VERSION" < "$LATEST_TAG" ]]; then
  echo "Error: Version $NEW_VERSION is less than current version $LATEST_TAG"
  exit 1
fi

Suggested change

	else
	# Validation: prevent duplicate tags and version downgrades
	if git tag -l "$NEW_VERSION" | grep -q "$NEW_VERSION"; then
	echo "Error: Version $NEW_VERSION already exists as a tag"
	exit 1
	fi
	# Compare versions (strip 'v' prefix)
	if [ "$(printf '%s\n' "${BUMP_TYPE}" "${CURRENT_VERSION}" | sort -V | tail -n1)" != "${BUMP_TYPE}" ]; then
	echo "Error: Version $NEW_VERSION is not greater than current version v${CURRENT_VERSION}"
	exit 1
	fi