Skip to content

Conversation

aomegax
Copy link
Contributor

@aomegax aomegax commented Oct 8, 2025

List of Changes

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as
    expected)

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

Copy link
Contributor

github-actions bot commented Oct 8, 2025

This pull request does not contain a valid label. Please add one of the following labels: [major, minor, patch, patch, skip]

Copy link
Contributor

github-actions bot commented Oct 8, 2025

The default action is to increase the PATCH number of SEMVER. Set IGNORE-FOR-RELEASE if you want to skip SEMVER bump. BREAKING-CHANGE and NEW-RELEASE must be run from GH Actions section manually.

@github-actions github-actions bot added the patch label Oct 8, 2025
Copy link
Contributor

github-actions bot commented Oct 8, 2025

The default action is to increase the PATCH number of SEMVER. Set IGNORE-FOR-RELEASE if you want to skip SEMVER bump. BREAKING-CHANGE and NEW-RELEASE must be run from GH Actions section manually.

@aomegax aomegax changed the title tuning memory fix: Tuning cpu, memory and autoscaling trigger Oct 8, 2025
@aomegax aomegax marked this pull request as ready for review October 9, 2025 15:37
@aomegax aomegax requested a review from a team as a code owner October 9, 2025 15:37
@aomegax aomegax merged commit 1cea221 into main Oct 9, 2025
6 checks passed
@aomegax aomegax deleted the tuning-prod branch October 9, 2025 15:41
Copy link

sonarqubecloud bot commented Oct 9, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants