chore: Bump to version 0.45.0 to start release process#4088
chore: Bump to version 0.45.0 to start release process#4088Xuanwo merged 6 commits intoapache:mainfrom
Conversation
|
Sorry for my misoperation😥 |
| @@ -1,289 +0,0 @@ | |||
| crate 0BSD Apache-2.0 Apache-2.0 WITH LLVM-exception BSD-2-Clause BSD-3-Clause BSL-1.0 CC0-1.0 ISC MIT MPL-2.0 OpenSSL Unicode-DFS-2016 Unlicense Zlib | |||
There was a problem hiding this comment.
Looks strange. Why this file is cleared?
There was a problem hiding this comment.
Fixed. (My apologies, I overlooked the [workspace.dependencies] version in Cargo.toml. Since this version doesn't include the patch version, when I searched for the last version, which is 0.44.2, it didn't show up.)
Line 61 in ddca18b
|
Hi, @morristai, please only push tags from the |
Sorry, my mistake. Can it be reverted? |
No, we cannot remove a tag that has already been pushed. Fortunately, our build for rc1 failed, so we now need to push an rc.2 tag which will not impact our subsequent steps. |
|
Just FYI: For the unfinished task - Update |
Let me update it. |
|
Hi, there are many changes after this PR created. Would you like to re-generate the changelog? Thanks! |
Should we create a version branch to lock on the feature and bugfix we need |
Too complex for our project, not interested. |
|
Should we also update the Haskell binding version in |
The haskell binding will have separate release processes. Let's pin 0.44.2 for haskell and remove the path in it. |
Done!
Addressed |
|
@Xuanwo Now I can push |
Yes! Please push a tag on main branch 🥰 |
What's Changed
Added
Changed
IntoFuturefor operator futures to remove an alloc by @Xuanwo in refactor: ImplementIntoFuturefor operator futures to remove an alloc #4098Fixed
Docs
CI
Chore
New Contributors