Enhace tag creation workflows

[spartan-ductduong]

Summary

Enhance tag creation workflows

Why

To ensure a major tag is created or updated each time a patch or minor tags is created.

• ❌ Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 🚀 New feature (non-breaking change which adds functionality)
• 🕷 Bug fix (non-breaking change which fixes an issue)
• 👏 Performance optimization (non-breaking change which addresses a performance issue)
• 🛠 Refactor (non-breaking change which does not change existing behavior or add new functionality)
• 📗Library update (non-breaking change that will update one or more libraries to newer versions)
• 📝 Documentation (non-breaking change that doesn't change code behavior, can skip testing)
• ✅ Test (non-breaking change related to testing)
• 🔒 Security awareness (changes that effect permission scope, security scenarios)

Test Plan

Checklist:

• I have performed a self-review of my own code
• I have tested that the feature or bug fix works as expected
• I have included helpful comments, particularly in hard-to-understand areas
• I have added tests that prove my changes are functioning
• New and existing unit tests pass locally with my changes

Related Issues