fix: CE 1124

[nayr974]

Description

Changes the way the appropriate git tag is selected. Instead of using git describe --tags to select the tag, which is only returning the first tag it uses git tag --merged which should select all tags that have been merged into the current branch. It's not clear exactly why git describe isn't working, but it has different logic to select the best or closest tag based on the branch history, not necessarily the newest tag.

References:
https://git-scm.com/docs/git-describe
https://stackoverflow.com/questions/67190989/when-and-why-exactly-does-git-describe-not-show-the-latest-tag

Question:

• How are branches merged into main?

How Has This Been Tested?

TBD

Checklist

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Further comments

---

Thanks for the PR!

Deployments, as required, will be available below:

• Frontend
• Backend

Please create PRs in draft mode. Mark as ready to enable:

• Analysis Workflow

After merge, new images are deployed in:

• Merge Workflow

---

Thanks for the PR!

Deployments, as required, will be available below:

• Frontend
• Backend

Please create PRs in draft mode. Mark as ready to enable:

• Analysis Workflow

After merge, new images are deployed in:

• Merge Workflow

---

Thanks for the PR!

Deployments, as required, will be available below:

• Frontend
• Backend

Please create PRs in draft mode. Mark as ready to enable:

• Analysis Workflow

After merge, new images are deployed in:

• Merge Workflow

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud