Set expected-version to release.tag_name for release events.

[mjohanse-emr]

What does this Pull Request accomplish?

Changes the default expected-version value so that release events use github.event.release.tag_name instead of github.ref_name. All non-release events will continue to use ref_name.

Why should this Pull Request be merged?

AB#3176680

What testing has been done?

I created a fork of nitypes-python and tried publishing to testpypi using my updated action.
https://github.com/mjohanse-emr/nitypes-python/actions/runs/15974070397
The job failed, but build step that contains check-project-version succeeded. The job failure appears to be because I don't have publish permissions on this repo.

PR checks for this repo succeeded.

[mjohanse-emr]

@mshafer-NI @bkeryan

Is there a way to test this change before submission by publishing a package to test PyPi? Maybe I can change the SHA on the check-project-version call to point to the commit in my dev branch?

[bkeryan]

@mshafer-NI @bkeryan

Is there a way to test this change before submission by publishing a package to test PyPi? Maybe I can change the SHA on the check-project-version call to point to the commit in my dev branch?

Yes. Here's how:

• Make a personal fork of nitypes-python
• Do this: bkeryan/nitypes-python@532d25e
• Change the SHA to point to your ni/python-actions dev branch
• Create a release in your personal fork

[mjohanse-emr]

@bkeryan @mshafer-NI

I created a fork of nitypes-python and tried publishing to testpypi using my updated action.
https://github.com/mjohanse-emr/nitypes-python/actions/runs/15974070397
The job failed, but build step that contains check-project-version succeeded. The job failure appears to be because I don't have publish permissions on this repo.

I'm not sure it's actually necessary to complete the entire publish process since the step that I was trying to fix succeeded, but I'll leave that up to y'all.

[bkeryan]

@bkeryan @mshafer-NI

I created a fork of nitypes-python and tried publishing to testpypi using my updated action. https://github.com/mjohanse-emr/nitypes-python/actions/runs/15974070397 The job failed, but build step that contains check-project-version succeeded. The job failure appears to be because I don't have publish permissions on this repo.

Your user account has publish permissions: https://test.pypi.org/project/nitypes/

However, your fork of the Git repo does not. You can login to TestPyPI and add your fork of the repo as a second trusted publisher if you want.

I'm not sure it's actually necessary to complete the entire publish process since the step that I was trying to fix succeeded, but I'll leave that up to y'all.

That's correct. The testing you did is sufficient to confirm that the updated check-project-version works from a release event.