update version to 0.11.2 and fix indexmap test #216
Merged
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
Signed-off-by: Lan <gcslyp@gmail.com>
liangyuanpeng
commented
Jun 14, 2025
| [package] | ||
| name = "kcl-lang" | ||
| version = "0.11.1" | ||
| version = "0.11.2" |
Contributor
Author
There was a problem hiding this comment.
I think this version should update first when release, no? cc @zong-zhe
liangyuanpeng
commented
Jun 14, 2025
| use kclvm_loader::{load_packages, LoadPackageOptions}; | ||
| use kclvm_parser::LoadProgramOptions; | ||
| use kclvm_runtime::{Context, IndexMap, PluginFunction, ValueRef}; | ||
| use kclvm_primitives::IndexMap; |
Contributor
Author
There was a problem hiding this comment.
Breaking change in kcl-lang/kcl#1952
cc @Peefy
liangyuanpeng
changed the title
Contributor
|
Good Catch! LGTM |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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: