Automation of github release and tag, and publish to pypi

[andrewelamb]

• Fixes FDS-1613
• Previous publish workflow renamed to publish-tag
• Previous publish workflow now only trgiggered on non-standard tags being created (ie. 24.4.1.dev)
• New publish workflow (publish-main) triggered on push to main
• New publish workflow: The github tag and release are created
• New publish workflow: Pypi release is done on push to main
• New publish workflow: Automates the creation of the release tag using todays date and number of releases previously this month

The tag regex has been improved to:

^v[1-9][0-9]\.[0-9]+\.[0-9]\.[a-z]+$

• The periods have been escaped as those are wild cards without doing so
• The starting and ending special characters added
• The \.[a-z]+ added means that
• v24.4.1 or v24.4.1-dev won't trigger the workflow
• v24.4.1.dev will trigger the workflow

[andrewelamb]

@linglp @mialy-defelice Coudl you look at the changes I just made? To solve the problems we dicussed on Wednesday, there are now two workflows.

[linglp]

Even if we want to keep two workflows, can we clean up this workflow more? Here, this workflow will still get triggered because branches: [main]

[andrewelamb]

Oh maybe I misunderstand how this works, but I thought this would require both the branch to be main and the tag to match. Otherwise this would have been triggered before every time we pushed to main right?

[andrewelamb]

I went ahead and removed that line

[linglp]

@andrewelamb could you also make sure tags like v0.1.16-beta won't trigger the workflow and make a PYPI release? Because that's a tag that we want to use to build a docker image for docker deployment, and not for PYPI release.

[sonarcloud]

Quality Gate passed

Issues
11 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[andrewelamb]

@linglp the regex for the tag is now:

- 'v[1-9][0-9].[0-9]+.[0-9].[a-z]+'

See the description above. I tested this out here:

https://regex101.com/

[linglp]

the old workflow is still referencing override_version.py right? So if you delete override_version.py, the old workflow will fail?

[andrewelamb]

@linglp Good point I'll make that fix

[linglp]

@andrewelamb additionally, I tried testing if dev tags will get tirggered by your regex, but it didn't seem to work. Github regex is different from regular regex... I found out when I was working on the docker publish workflow that even though an external tool might say that xx would work given a regex rule, it might still not work for github.

To reproduce :

1. check out branch: develop-test-fds-1613
2. create a tag, like v24.4.1.dev
3. push that tag to schematic repo..

When I checked the github action tab, the workflow didn't get triggered. And then you could remove the tag both locally and remotely

[linglp]

@andrewelamb if you are not going to continue working on this, can this PR be closed?

[andrewelamb]

@linglp Yep!

[andrewelamb]

I'm going to leave the branch for now in case anyoen wants to take a crack at it in the near future.