[TD-2193] Use correct tags for CI push and CI test

[alephnull]

The old architecture of doing ci in a separate job made the larger workflow seemingly more resilient but as the automation grows, failures in CI will make the remainder of the release process unprocessable. So doubling down on making CI push robust.

Removed ci/auto as it lives in tyk-ci now. Tested by re-using v5.2.1-alpha.

I will propagate this fix to gw and dash master and lts branches via templates, the fix will have to be cherry picked for other branches where it is required. Please review https://github.com/TykTechnologies/tyk-analytics/pull/3429 along with this one.

[github-actions]

PR Analysis

• 🎯 Main theme: Updating the CI/CD pipeline to use correct tags for CI push and CI test
• 📌 Type of PR: Refactoring
• ✨ Focused PR: Yes, all changes are related to the CI/CD pipeline and tagging.
• 🔒 Security concerns: No security concerns found

PR Feedback

• General suggestions: The changes in this PR seem to be well thought out and are a good step towards improving the CI/CD pipeline. However, it would be beneficial to add some tests to ensure the changes work as expected.

• 🤖 Code feedback:

  • relevant file: .github/workflows/release.yml
    suggestion: Consider using a script file to handle the complex logic in the 'run' section. This will make the code more readable and maintainable. [medium]
    relevant line: run: |

  • relevant file: .github/workflows/release.yml
    suggestion: It's a good practice to avoid hardcoding values like 'amd64' and 'arm64'. Consider using environment variables or configuration files to store these values. [medium]
    relevant line: for arch in amd64 arm64; do

  • relevant file: .github/workflows/release.yml
    suggestion: It's recommended to handle errors in the script. The 'set +e' command prevents the script from exiting when a command fails. This could lead to unexpected behavior. [important]
    relevant line: set +e

How to use

To invoke the PR-Agent, add a comment using one of the following commands:
/review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option.
/describe: Modify the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest improvements to the code in the PR. Extended mode employs several calls, and provides a more thorough feedback.
/ask <QUESTION>: Pose a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.

To edit any configuration parameter from configuration.toml, add --config_path=new_value
For example: /review --pr_reviewer.extra_instructions="focus on the file: ..."
To list the possible configuration parameters, use the /config command.

[github-actions]

API Changes

no api changes detected

[Tyk-ITS]

API tests result: success ✅
Branch used: refs/pull/5465/merge
Commit:
Triggered by: pull_request (@alephnull)
Execution page

[Tyk-ITS]

API tests result: success ✅
Branch used: refs/pull/5465/merge
Commit: f406dcc
Triggered by: pull_request (@alephnull)
Execution page

[Tyk-ITS]

API tests result: failure 🚫
Branch used: refs/pull/5465/merge
Commit: 96ae1ad
Triggered by: pull_request (@alephnull)
Execution page

[Tyk-ITS]

API tests result: success ✅
Branch used: refs/pull/5465/merge
Commit: e1951a3
Triggered by: pull_request (@alephnull)
Execution page

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[Tyk-ITS]

API tests result: success ✅
Branch used: refs/pull/5465/merge
Commit: 191404f
Triggered by: pull_request (@alephnull)
Execution page

[asutosh]

/release to release-5.2.1

[tykbot]

Working on it! Note that it can take a few minutes.

[tykbot]

@asutosh Succesfully merged PR