Kuperator v0.6.5 #123
Merged
Kuperator v0.6.5 #123
+7,663
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Eikykun
approved these changes
Nov 7, 2025
ColdsteelRail
added a commit
that referenced
this pull request
Nov 21, 2025
<!-- Thank you for contributing to KusionStack!
Note:
1. With pull requests:
- Open your pull request against "main"
- Your pull request should have no more than two commits, if not you
should squash them.
- It should pass all tests in the available continuous integration
systems such as GitHub Actions.
- You should add/modify tests to cover your proposed code changes.
- If your pull request contains a new feature, please document it on the
README.
2. Please create an issue first to describe the problem.
We recommend that link the issue with the PR in the following question.
For more info, check https://kusionstack.io/docs/governance/contribute/
-->
#### 1. Does this PR affect any open issues?(Y/N) and add issue
references (e.g. "fix #123", "re #123".):
- [ ] N
- [ ] Y
<!-- You can add issue references here.
e.g.
fix #123, re #123,
fix https://github.com/XXX/issues/44
-->
#### 2. What is the scope of this PR (e.g. component or file name):
<!-- You can add the scope of this change here.
e.g.
/src/server/core.rs,
kusionstack/KCLVM/kclvm-parser
-->
#### 3. Provide a description of the PR(e.g. more details, effects,
motivations or doc link):
<!-- You can choose a brief description here -->
- [ ] Affects user behaviors
- [ ] Contains syntax changes
- [ ] Contains variable changes
- [ ] Contains experimental features
- [ ] Performance regression: Consumes more CPU
- [ ] Performance regression: Consumes more Memory
- [ ] Other
<!-- You can add more details here.
e.g.
Call method "XXXX" to ..... in order to ....,
More details: https://XXXX.com/doc......
-->
#### 4. Are there any breaking changes?(Y/N) and describe the breaking
changes(e.g. more details, motivations or doc link):
- [ ] N
- [ ] Y
<!-- You can add more details here.
e.g.
Calling method "XXXX" will cause the "XXXX", "XXXX" modules to be
affected.
More details: https://XXXX.com/doc......
-->
#### 5. Are there test cases for these changes?(Y/N) select and add more
details, references or doc links:
<!-- You can choose a brief description here -->
- [ ] Unit test
- [ ] Integration test
- [ ] Benchmark (add benchmark stats below)
- [ ] Manual test (add detailed scripts or steps below)
- [ ] Other
<!-- You can add more details here.
e.g.
The test case in XXXX is used to .....
test cases in /src/tests/XXXXX
test cases https://github.com/XXX/pull/44
benchmark stats: time XXX ms
-->
#### 6. Release note
<!-- compatibility change, improvement, bugfix, and new feature need a
release note -->
Please refer to [Release Notes Language Style
Guide](https://kusionstack.io/docs/governance/release-policy/) to write
a quality release note.
```release-note
None
```
ColdsteelRail
added a commit
that referenced
this pull request
Nov 28, 2025
<!-- Thank you for contributing to KusionStack!
Note:
1. With pull requests:
- Open your pull request against "main"
- Your pull request should have no more than two commits, if not you
should squash them.
- It should pass all tests in the available continuous integration
systems such as GitHub Actions.
- You should add/modify tests to cover your proposed code changes.
- If your pull request contains a new feature, please document it on the
README.
2. Please create an issue first to describe the problem.
We recommend that link the issue with the PR in the following question.
For more info, check https://kusionstack.io/docs/governance/contribute/
-->
#### 1. Does this PR affect any open issues?(Y/N) and add issue
references (e.g. "fix #123", "re #123".):
- [ ] N
- [ ] Y
<!-- You can add issue references here.
e.g.
fix #123, re #123,
fix https://github.com/XXX/issues/44
-->
#### 2. What is the scope of this PR (e.g. component or file name):
<!-- You can add the scope of this change here.
e.g.
/src/server/core.rs,
kusionstack/KCLVM/kclvm-parser
-->
#### 3. Provide a description of the PR(e.g. more details, effects,
motivations or doc link):
<!-- You can choose a brief description here -->
- [ ] Affects user behaviors
- [ ] Contains syntax changes
- [ ] Contains variable changes
- [ ] Contains experimental features
- [ ] Performance regression: Consumes more CPU
- [ ] Performance regression: Consumes more Memory
- [ ] Other
<!-- You can add more details here.
e.g.
Call method "XXXX" to ..... in order to ....,
More details: https://XXXX.com/doc......
-->
#### 4. Are there any breaking changes?(Y/N) and describe the breaking
changes(e.g. more details, motivations or doc link):
- [ ] N
- [ ] Y
<!-- You can add more details here.
e.g.
Calling method "XXXX" will cause the "XXXX", "XXXX" modules to be
affected.
More details: https://XXXX.com/doc......
-->
#### 5. Are there test cases for these changes?(Y/N) select and add more
details, references or doc links:
<!-- You can choose a brief description here -->
- [ ] Unit test
- [ ] Integration test
- [ ] Benchmark (add benchmark stats below)
- [ ] Manual test (add detailed scripts or steps below)
- [ ] Other
<!-- You can add more details here.
e.g.
The test case in XXXX is used to .....
test cases in /src/tests/XXXXX
test cases https://github.com/XXX/pull/44
benchmark stats: time XXX ms
-->
#### 6. Release note
<!-- compatibility change, improvement, bugfix, and new feature need a
release note -->
Please refer to [Release Notes Language Style
Guide](https://kusionstack.io/docs/governance/release-policy/) to write
a quality release note.
```release-note
None
```
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):
2. What is the scope of this PR (e.g. component or file name):
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):
4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):
5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:
6. Release note
Please refer to Release Notes Language Style Guide to write a quality release note.