Support Minor Version Tagging

[hazeltonl]

• All tests passed. If this feature is not already covered by the tests, I added new tests.
• I used npm run format for formatting the code before submitting the pull request.

---

PR Description: Enable Versioning by Minor Versions for [email protected]

This update introduces support for specifying minor versions of the action. Previously, you could only use action@v4 to point to the latest release of the major version v4. With this change, you can now pin your workflow to specific minor versions, offering greater flexibility and stability.

What’s New:

• Minor version tagging: You can now specify versions such as [email protected] to use the latest minor version of v4.
• This allows you to fix your workflow to a specific minor version and benefit from bug fixes or improvements within that minor version without automatically upgrading to a new major version.

How to Use:

To use this feature, simply replace action@v4 with [email protected] in your GitHub Actions workflows. This change ensures that your workflows will continue using the latest patch updates within the specified minor version.

Example 1: Using action@v4 for the latest major version (before the update):

uses: actions/action-name@v4

Example 2: Pinning to the latest minor version of v4 (v4.x):

uses: actions/[email protected]

With this configuration, GitHub Actions will use the latest minor release of v4, ensuring your workflow remains stable within the same major version while benefiting from any fixes or improvements within the minor version.

Why This is Useful:

• Improved Stability: You can now be more specific about the version you're using, preventing unexpected updates that might come with new major releases.
• Flexible Upgrades: This allows for smoother upgrades when minor version improvements are made without jumping to a new major version.

Example Use Case:

If you want to lock your workflow to the latest release of version 4, but ensure it doesn't automatically upgrade to a future major version (like v5), you can now use:

uses: actions/[email protected]

This ensures you're always using the latest features and bug fixes within the v4 series without risking breaking changes from a new major release.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[hazeltonl]

I have read the CLA Document and I hereby sign the CLA

[hazeltonl]

recheck

[hazeltonl]

I tested the automatic release functionality in my forked repo and it works the same and manually creating a Release with generated release notes.

[hazeltonl]

recheck

[hazeltonl]

@EyalDelarea I'm not sure how to request reviewer(s)

[hazeltonl]

@eyalbe4 I'm not sure how to request reviewer(s)

[hazeltonl]

@RobiNino could you please review / add reviewers on my behalf?

[hazeltonl]

@sverdlov93 Are public users allowed to propose these types of changes? I don't think I've missed any steps in the contributing guidelines

[hazeltonl]

@EyalDelarea @eyalb4doc @RobiNino @sverdlov93 Is this a welcome change? Maybe you guys have some insight on a different way to approach this?

[EyalDelarea]

Hi @hazeltonl,

Thank you for your contribution!

We appreciate your effort, but unfortunately, automating releases isn’t a suitable approach for our workflow. Since this action is customer-facing, we usually prefer to edit the release notes before publishing. Editing them after release isn't ideal for us because customers are notified immediately.

That said, adding minor version tagging is a great improvement. If you'd like to adjust your PR to include only the minor tagging feature, I’d be happy to review it.

Thank you again for your support!

[hazeltonl]

@EyalDelarea that makes total sense! Easy change then, already pushed :)