HMS-10377: fix semantic release workflow

[TenSt]

Secure Coding Practices Checklist GitHub Link

• https://github.com/RedHatInsights/secure-coding-checklist

Secure Coding Checklist

• Input Validation
• Output Encoding
• Authentication and Password Management
• Session Management
• Access Control
• Cryptographic Practices
• Error Handling and Logging
• Data Protection
• Communication Security
• System Configuration
• Database Security
• File Management
• Memory Management
• General Coding Practices

Summary by Sourcery

Replace the previous semantic-release workflow with a new GitHub Actions setup that automatically bumps the project version, opens a release PR, and creates GitHub releases based on the VERSION file.

Build:

• Add a scheduled and manually-triggerable workflow to increment the VERSION file, update OpenAPI docs, and open a release pull request for the next semantic version.
• Add a workflow that tags and creates a GitHub release whenever the VERSION file is updated on the main branch.
• Remove the legacy semantic-release GitHub Actions workflow in favor of the new release process.

[sourcery-ai]

Reviewer's Guide

Replaces the previous semantic-release workflow with a two-step GitHub Actions process that automatically bumps the VERSION file and OpenAPI docs on a schedule or PR trigger, opens a release PR, and on merge creates a GitHub release from the VERSION tag.

File-Level Changes

Change	Details	Files
Introduce scheduled workflow to bump version, update OpenAPI docs, and open a release PR.	Add release-create-pr workflow triggered by cron, workflow_dispatch, and pull_request events Checkout repository using latest v6 of actions/checkout Determine next semantic version based on VERSION file and last commit message suffix (/major, /minor, /patch) via increment_version.sh Update OpenAPI JSON version fields and VERSION file to the next version, and expose it via GITHUB_OUTPUT Create a pull request from a version-specific branch with updated files using peter-evans/create-pull-request	.github/workflows/release-create-pr.yml
Add workflow to create a GitHub release whenever the VERSION file is updated on main.	Add create-release workflow triggered by pushes to main that modify the VERSION file Checkout repository using actions/checkout@v4 Read tag value from VERSION file and publish a GitHub release using softprops/action-gh-release with generated notes and marked as latest	.github/workflows/create-release.yml
Remove legacy semantic-release workflow in favor of new VERSION-based release process.	Delete semantic-release.yml workflow file to disable the old semantic-release process	.github/workflows/semantic-release.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[github-actions]

SC Environment Impact Assessment

Overall Impact: ⚪ NONE

No SC Environment-specific impacts detected in this PR.

What was checked

This PR was automatically scanned for:

• Database migrations
• ClowdApp configuration changes
• Kessel integration changes
• AWS service integrations (S3, RDS, ElastiCache)
• Kafka topic changes
• Secrets management changes
• External dependencies

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.18%. Comparing base (ce50174) to head (a0f8c3b).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2120   +/-   ##
=======================================
  Coverage   59.18%   59.18%           
=======================================
  Files         134      134           
  Lines        8622     8622           
=======================================
  Hits         5103     5103           
  Misses       2984     2984           
  Partials      535      535           

Flag	Coverage Δ
unittests	59.18% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.