Fix deploy_release.yml tag pattern to trigger on version tags

[Copilot]

Overview:

The deploy_release.yml workflow was not triggering on version tags like v2.1.1 due to an incorrect filter pattern. The pattern '^v[0-9]+.[0-9]+.[0-9]+' used ^ as a negation operator (matching tags that do NOT match the pattern) and unescaped dots (matching any character instead of literal dots).

Addresses:

This addresses the workflow trigger issue for semantic version tags.

Type of Fix:

• 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 Change

Solution:

Changed the tag filter pattern from '^v[0-9]+.[0-9]+.[0-9]+' to 'v[0-9]+\.[0-9]+\.[0-9]+':

• Removed ^ (negation operator in GitHub Actions filters)
• Escaped dots to match literal dots in semantic versions

Changes:

• Updated .github/workflows/deploy_release.yml line 5 with corrected tag pattern
• Pattern now matches: v2.1.1, v1.0.0, v10.20.30
• Pattern rejects: v1a2b3, non-version tags

Validation:

Per GitHub Actions documentation, ^ at pattern start negates the match. Workflow will now trigger on push of semantic version tags.

Unit Tests:

N/A - workflow configuration change

Configuration details:

GitHub Actions workflow trigger pattern syntax

Checklist

• My code follows Allen Institute Contribution Guidelines
• My code is unit tested and does not decrease test coverage
• I have performed a self review of my own code
• My code is well-documented, and the docstrings conform to Numpy Standards
• I have updated the documentation of the repository where appropriate
• The header on my commit includes the issue number
• My code passes all tests
• I have updated the CHANGELOG.md with the description of changes understandable by end users

Notes:

Reference: GitHub Actions filter pattern cheat sheet

Original prompt

On deploy_release.yml, Why is this workflow not triggered for the tag v2.1.1?

---

💡 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.

[t-b]

Escaped dots to match literal dots in semantic versions

This is BS.