From 835f588180522df33842fa619744f57cd3034c5a Mon Sep 17 00:00:00 2001 From: Liuqing Yue Date: Sun, 31 Dec 2023 11:44:11 +0800 Subject: [PATCH] chore: update release related docs and script (#3870) --- scripts/release.sh | 7 ++++++- website/community/committers/release.md | 3 +-- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/scripts/release.sh b/scripts/release.sh index 94ec586ea5d..2217047d732 100755 --- a/scripts/release.sh +++ b/scripts/release.sh @@ -53,7 +53,12 @@ PACKAGES=( "integrations\/" ) for package in "${PACKAGES[@]}"; do - sed -i "/${package}/d" Cargo.toml + if [[ "$OSTYPE" == "darwin"* ]]; then + # macOS system sed usage is different from others + sed -i '' "/${package}/d" Cargo.toml + else + sed -i "/${package}/d" Cargo.toml + fi done echo "> Start package" diff --git a/website/community/committers/release.md b/website/community/committers/release.md index 2db0f9681c3..6b457beacbc 100644 --- a/website/community/committers/release.md +++ b/website/community/committers/release.md @@ -158,8 +158,7 @@ After bump version PR gets merged, we can create a GitHub release for the releas - Create a tag at `main` branch on the `Bump Version` / `Patch up version` commit: `git tag -s "v0.36.0-rc.1"`, please correctly check out the corresponding commit instead of directly tagging on the main branch. - Push tags to GitHub: `git push --tags`. -- Create Release on the newly created tag - - If there are breaking changes, please add the content from `upgrade.md` before. + :::note