chore: bump purego to 1638563e361522e5f63511d84c4541ae1c5fd704 to fix…#234
Merged
Peefy merged 1 commit intokcl-lang:mainfrom May 10, 2025
Merged
chore: bump purego to 1638563e361522e5f63511d84c4541ae1c5fd704 to fix…#234Peefy merged 1 commit intokcl-lang:mainfrom
Peefy merged 1 commit intokcl-lang:mainfrom
Conversation
… 1.24.3 problem Signed-off-by: Lan Liang <gcslyp@gmail.com>
Pull Request Test Coverage Report for Build 14933090316Details
💛 - Coveralls |
Contributor
Author
|
CI is green: https://github.com/kcl-lang/cli/actions/runs/14933090316/job/41954041646?pr=234 , so it's working now. |
Contributor
|
Amazing Job! LGTM |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.24.3 problem
releated:
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: