Skip to content

fix: compatibility with go1.18 #127

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 12, 2025
Merged

fix: compatibility with go1.18 #127

merged 1 commit into from
Jun 12, 2025

Conversation

ppzqh
Copy link
Contributor

@ppzqh ppzqh commented Jun 11, 2025

What type of PR is this?

Check the PR title.

  • This PR title match the format: <type>(optional scope): <description>
  • The description of this PR title is user-oriented and clear enough for others to understand.
  • Attach the PR updating the user documentation if the current PR requires user awareness at the usage level. User docs repo

(Optional) Translate the PR title into Chinese.

(Optional) More detailed description for this PR(en: English/zh: Chinese).

en:
zh(optional):

(Optional) Which issue(s) this PR fixes:

(optional) The PR that updates user documentation:

@ppzqh ppzqh requested review from a team as code owners June 11, 2025 12:44
@ppzqh ppzqh force-pushed the test_1.18 branch 2 times, most recently from 4fa5946 to b206391 Compare June 12, 2025 01:05
@ppzqh ppzqh changed the title chore: compatible with go 1.18 fix: compatibility with go1.18 Jun 12, 2025
@ppzqh ppzqh force-pushed the test_1.18 branch 2 times, most recently from 325447e to 63b0cbe Compare June 12, 2025 03:11
@ppzqh ppzqh merged commit 497c29b into main Jun 12, 2025
3 checks passed
@ppzqh ppzqh deleted the test_1.18 branch June 12, 2025 03:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants