forked from youki-dev/youki
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Release for v0.4.2 #2
Open
github-actions
wants to merge
7
commits into
main
Choose a base branch
from
tagpr-from-v0.4.1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
github-actions
bot
force-pushed
the
tagpr-from-v0.4.1
branch
from
November 18, 2024 07:16
6f75047
to
791b1d8
Compare
github-actions
bot
force-pushed
the
tagpr-from-v0.4.1
branch
2 times, most recently
from
November 28, 2024 23:26
29db647
to
27ffb25
Compare
github-actions
bot
force-pushed
the
tagpr-from-v0.4.1
branch
5 times, most recently
from
December 6, 2024 04:32
5ad71f9
to
96bd24c
Compare
github-actions
bot
force-pushed
the
tagpr-from-v0.4.1
branch
from
December 6, 2024 04:51
96bd24c
to
8ad2d7f
Compare
* refactor(test): refine function create_container add CreateOptions as para to function create_container for create container with different options Signed-off-by: xujihui1985 <xujihui1985@gmail.com> * fix: fix failed unittest Signed-off-by: xujihui1985 <xujihui1985@gmail.com> --------- Signed-off-by: xujihui1985 <xujihui1985@gmail.com>
* fix(libcontainer): combine multi error when create container failed When container creation fails and triggers a cleanup process that also fails, the original creation error is overwritten by the cleanup error. This change ensures that both the primary creation error and the subsequent cleanup error are captured and reported, providing better visibility into the failure sequence. Signed-off-by: xujihui1985 <xujihui1985@gmail.com> * fix: fix lint error Signed-off-by: xujihui1985 <xujihui1985@gmail.com> * refactor(libcontainer): add CreateContainerError add CreateContainerError to encapsulate both create error and cleanup error, so that caller will understand what happened Signed-off-by: xujihui1985 <xujihui1985@gmail.com> * refactor(libcontainer): use tuple instead of struct change createContainerError to tuple instead of struct Signed-off-by: xujihui1985 <xujihui1985@gmail.com> --------- Signed-off-by: xujihui1985 <xujihui1985@gmail.com>
…ki-dev#2966) Signed-off-by: Abel Feng <fshb1988@gmail.com> Signed-off-by: Yashodhan Joshi <yjdoc2@gmail.com> Co-authored-by: Yashodhan Joshi <yjdoc2@gmail.com>
* add test root readonly true Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * fix test group name Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * fix format Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * remove blank line Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * remove unused import Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * fix format err Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * remove unnecessary return Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * separate test root readonly true and false Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * fix format err Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * change test_dir_write_access to pub fn to use test Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * check root readonly to use test_dir_write_access Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * fix format err Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * fix format err Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * remove blank line Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * separate two tests to root_readonly_true and root_readonly_false Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * change test_dir_read_access to pub fn to use test Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * fix debug message and add check read access Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * fix format err Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * add root_readonly test to main Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * add read access test when root readonly is false Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * fox type err Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * remove code err to raw os err Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> * add CreateOptions Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com> --------- Signed-off-by: sat0ken <15720506+sat0ken@users.noreply.github.com>
Bumps the patch group with 2 updates: [thiserror](https://github.com/dtolnay/thiserror) and [anyhow](https://github.com/dtolnay/anyhow). Updates `thiserror` from 2.0.3 to 2.0.4 - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](dtolnay/thiserror@2.0.3...2.0.4) Updates `anyhow` from 1.0.93 to 1.0.94 - [Release notes](https://github.com/dtolnay/anyhow/releases) - [Commits](dtolnay/anyhow@1.0.93...1.0.94) --- updated-dependencies: - dependency-name: thiserror dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch - dependency-name: anyhow dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch ... Signed-off-by: dependabot[bot] <support@github.com>
github-actions
bot
force-pushed
the
tagpr-from-v0.4.1
branch
from
December 6, 2024 04:51
8ad2d7f
to
799cbc6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request is for the next release as v0.4.2 created by tagpr. Merging it will tag v0.4.2 to the merge commit and create a GitHub release.
You can modify this branch "tagpr-from-v0.4.1" directly before merging if you want to change the next version number or other files for the release.
How to change the next version as you like
There are two ways to do it.
Full Changelog: v0.4.1...v0.4.2