Skip to content

chore: release v0.9.6 #1282

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 20 commits into from
Feb 26, 2025
Merged

chore: release v0.9.6 #1282

merged 20 commits into from
Feb 26, 2025

Conversation

alice-yyds
Copy link
Contributor

No description provided.

xiaost and others added 20 commits January 3, 2025 16:38
@xiaost
ci(lint): new linter and new issues only (#1254)
a8d0648
@GuangmingLuo
chore: merge back v0.9.5 (#1256)
f3ed7a3 
#### What type of PR is this?
chore

#### Check the PR title.
<!--
The description of the title will be attached in Release Notes, 
so please describe it from user-oriented, what this PR does / why we
need it.
Please check your PR title with the below requirements:
-->
- [ ] 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](https://github.com/cloudwego/cloudwego.github.io)


#### (Optional) Translate the PR title into Chinese.


#### (Optional) More detailed description for this PR(en: English/zh:
Chinese).
<!--
Provide more detailed info for review(e.g., it's recommended to provide
perf data if this is a perf type PR).
-->
en:
zh(optional):

#### (Optional) Which issue(s) this PR fixes:
<!--
Automatically closes linked issue when PR is merged.
Eg: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->

#### (Optional) The PR that updates user documentation:
<!--
If the current PR requires user awareness at the usage level, please
submit a PR to update user docs. [User docs
repo](https://github.com/cloudwego/cloudwego.github.io)
-->
@xiaost
chore: upgrade sonic for fixing bin size issue (#1258)
cf51853
@xiaost
fix: ClientIP() handles uds instead of returning empty (#1264)
02dd68f
@HeyJavaBean
fix: fix hz gen file permission (#1262)
240d401
@shenfc6
test: add test in TestResponseReadBodyStream in the case of ErrBodyTo…
02acf0e 
…oLarge (#1221)
@xiaost
test(client): increase timeout for windows (#1268)
42c7b13
@AsterDY
feat: update sonic api and feature
f9bf02d
@AsterDY
feat: update
2b12f67
@GuangmingLuo
chore: update hertz readme description
d733215
@AsterDY
feat: update sonic build constraints (#1272)
a677f53 
#### What type of PR is this?
<!--
Add one of the following kinds:

build: Changes that affect the build system or external dependencies
(example scopes: gulp, broccoli, npm)
ci: Changes to our CI configuration files and scripts (example scopes:
Travis, Circle, BrowserStack, SauceLabs)
docs: Documentation only changes
feat: A new feature
optimize: A new optimization
fix: A bug fix
perf: A code change that improves performance
refactor: A code change that neither fixes a bug nor adds a feature
style: Changes that do not affect the meaning of the code (white space,
formatting, missing semi-colons, etc)
test: Adding missing tests or correcting existing tests
chore: Changes to the build process or auxiliary tools and libraries
such as documentation generation
-->
feat

#### Check the PR title.
<!--
The description of the title will be attached in Release Notes, 
so please describe it from user-oriented, what this PR does / why we
need it.
Please check your PR title with the below requirements:
-->
- [ ] 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](https://github.com/cloudwego/cloudwego.github.io)


#### (Optional) Translate the PR title into Chinese.


#### (Optional) More detailed description for this PR(en: English/zh:
Chinese).
<!--
Provide more detailed info for review(e.g., it's recommended to provide
perf data if this is a perf type PR).
-->
en: update sonic build constraints
zh(optional): 更新 sonic 编译条件

#### (Optional) Which issue(s) this PR fixes:
<!--
Automatically closes linked issue when PR is merged.
Eg: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->

#### (Optional) The PR that updates user documentation:
<!--
If the current PR requires user awareness at the usage level, please
submit a PR to update user docs. [User docs
repo](https://github.com/cloudwego/cloudwego.github.io)
-->
@GuangmingLuo
chore: update hertz readme description (#1273)
9249c6e 
#### What type of PR is this?
<!--
Add one of the following kinds:

build: Changes that affect the build system or external dependencies
(example scopes: gulp, broccoli, npm)
ci: Changes to our CI configuration files and scripts (example scopes:
Travis, Circle, BrowserStack, SauceLabs)
docs: Documentation only changes
feat: A new feature
optimize: A new optimization
fix: A bug fix
perf: A code change that improves performance
refactor: A code change that neither fixes a bug nor adds a feature
style: Changes that do not affect the meaning of the code (white space,
formatting, missing semi-colons, etc)
test: Adding missing tests or correcting existing tests
chore: Changes to the build process or auxiliary tools and libraries
such as documentation generation
-->

#### Check the PR title.
<!--
The description of the title will be attached in Release Notes, 
so please describe it from user-oriented, what this PR does / why we
need it.
Please check your PR title with the below requirements:
-->
- [ ] 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](https://github.com/cloudwego/cloudwego.github.io)


#### (Optional) Translate the PR title into Chinese.


#### (Optional) More detailed description for this PR(en: English/zh:
Chinese).
<!--
Provide more detailed info for review(e.g., it's recommended to provide
perf data if this is a perf type PR).
-->
en: update readme about doc and reference
zh(optional):

#### (Optional) Which issue(s) this PR fixes:
<!--
Automatically closes linked issue when PR is merged.
Eg: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->

#### (Optional) The PR that updates user documentation:
<!--
If the current PR requires user awareness at the usage level, please
submit a PR to update user docs. [User docs
repo](https://github.com/cloudwego/cloudwego.github.io)
-->
@xiaost
ci: use self-hosted windows for ut (#1274)
9c05c0a
@FGYFFFF
fix: filename with dot
486f330
@FGYFFFF
fix(hz): thrift filename with dot (#1275)
4c26262 
#### What type of PR is this?
<!--
Add one of the following kinds:

build: Changes that affect the build system or external dependencies
(example scopes: gulp, broccoli, npm)
ci: Changes to our CI configuration files and scripts (example scopes:
Travis, Circle, BrowserStack, SauceLabs)
docs: Documentation only changes
feat: A new feature
optimize: A new optimization
fix: A bug fix
perf: A code change that improves performance
refactor: A code change that neither fixes a bug nor adds a feature
style: Changes that do not affect the meaning of the code (white space,
formatting, missing semi-colons, etc)
test: Adding missing tests or correcting existing tests
chore: Changes to the build process or auxiliary tools and libraries
such as documentation generation
-->
fix
#### Check the PR title.
<!--
The description of the title will be attached in Release Notes, 
so please describe it from user-oriented, what this PR does / why we
need it.
Please check your PR title with the below requirements:
-->
- [ ] 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](https://github.com/cloudwego/cloudwego.github.io)


#### (Optional) Translate the PR title into Chinese.


#### (Optional) More detailed description for this PR(en: English/zh:
Chinese).
<!--
Provide more detailed info for review(e.g., it's recommended to provide
perf data if this is a perf type PR).
-->
en: thrift filename with dot
zh(optional): 修复 thrift 文件名带 "." 导致解析失败的问题

#### (Optional) Which issue(s) this PR fixes:
<!--
Automatically closes linked issue when PR is merged.
Eg: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->

#### (Optional) The PR that updates user documentation:
<!--
If the current PR requires user awareness at the usage level, please
submit a PR to update user docs. [User docs
repo](https://github.com/cloudwego/cloudwego.github.io)
-->
@GuangmingLuo
chore: rm release-check.yml
c295fbd 
Change-Id: I18db0f3224832d0c2adc49ed8c48d90c0d42b980
@GuangmingLuo
chore: rm release-check.yml (#1277)
0b0a02a 
Change-Id: I18db0f3224832d0c2adc49ed8c48d90c0d42b980

#### What type of PR is this?
<!--
Add one of the following kinds:

build: Changes that affect the build system or external dependencies
(example scopes: gulp, broccoli, npm)
ci: Changes to our CI configuration files and scripts (example scopes:
Travis, Circle, BrowserStack, SauceLabs)
docs: Documentation only changes
feat: A new feature
optimize: A new optimization
fix: A bug fix
perf: A code change that improves performance
refactor: A code change that neither fixes a bug nor adds a feature
style: Changes that do not affect the meaning of the code (white space,
formatting, missing semi-colons, etc)
test: Adding missing tests or correcting existing tests
chore: Changes to the build process or auxiliary tools and libraries
such as documentation generation
-->

#### Check the PR title.
<!--
The description of the title will be attached in Release Notes, 
so please describe it from user-oriented, what this PR does / why we
need it.
Please check your PR title with the below requirements:
-->
- [ ] 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](https://github.com/cloudwego/cloudwego.github.io)


#### (Optional) Translate the PR title into Chinese.


#### (Optional) More detailed description for this PR(en: English/zh:
Chinese).
<!--
Provide more detailed info for review(e.g., it's recommended to provide
perf data if this is a perf type PR).
-->
en:
zh(optional):

#### (Optional) Which issue(s) this PR fixes:
<!--
Automatically closes linked issue when PR is merged.
Eg: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->

#### (Optional) The PR that updates user documentation:
<!--
If the current PR requires user awareness at the usage level, please
submit a PR to update user docs. [User docs
repo](https://github.com/cloudwego/cloudwego.github.io)
-->
@Marina-Sakai
chore: add observability for max conns (#1279)
54b35c2
@Marina-Sakai
optimize(server): exit normally when getting SIGTERM (#1280)
463ad91
@alice-yyds
chore: update version v0.9.6
7c3893c
@alice-yyds alice-yyds requested review from a team as code owners February 26, 2025 06:16
@codecov Codecov
Copy link

codecov bot commented Feb 26, 2025 •
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.15%. Comparing base (be643ee) to head (7c3893c).
Report is 51 commits behind head on main.

❗ There is a different number of reports uploaded between BASE (be643ee) and HEAD (7c3893c). Click for more details.

HEAD has 1 upload less than BASE
Flag BASE (be643ee) HEAD (7c3893c)
2 1
Additional details and impacted files 
@@            Coverage Diff             @@
##             main    #1282      +/-   ##
==========================================
- Coverage   82.88%   73.15%   -9.73%     
==========================================
  Files          98      138      +40     
  Lines       10065    13533    +3468     
==========================================
+ Hits         8342     9900    +1558     
- Misses       1233     3036    +1803     
- Partials      490      597     +107

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@YangruiEmma YangruiEmma merged commit a320188 into main Feb 26, 2025
29 of 30 checks passed
@YangruiEmma YangruiEmma deleted the release-v0.9.6 branch February 26, 2025 10:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ppzqh ppzqh ppzqh approved these changes

+1 more reviewer

@Marina-Sakai Marina-Sakai Marina-Sakai approved these changes

Reviewers whose approvals may not affect merge requirements
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
10 participants
@alice-yyds @ppzqh @Marina-Sakai @YangruiEmma @xiaost @GuangmingLuo @HeyJavaBean @shenfc6 @AsterDY @FGYFFFF