Skip to content
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

v0.2.0 #2333

Merged
merged 1 commit into from
Sep 1, 2023
Merged

v0.2.0 #2333

merged 1 commit into from
Sep 1, 2023

Conversation

utam0k
Copy link
Member

@utam0k utam0k commented Aug 31, 2023

No description provided.

Signed-off-by: utam0k <[email protected]>
@utam0k utam0k requested a review from a team August 31, 2023 11:54
@codecov-commenter
Copy link

Codecov Report

Merging #2333 (c04a9a0) into main (0036180) will decrease coverage by 0.01%.
Report is 4 commits behind head on main.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2333      +/-   ##
==========================================
- Coverage   64.81%   64.80%   -0.01%     
==========================================
  Files         129      129              
  Lines       15171    15171              
==========================================
- Hits         9833     9832       -1     
- Misses       5338     5339       +1     

@utam0k utam0k added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Aug 31, 2023
@YJDoc2
Copy link
Collaborator

YJDoc2 commented Sep 1, 2023

Hey, do you want me to update the MirgationGuide.md file for this? Or is it fine to leave it as it is for now?

@utam0k
Copy link
Member Author

utam0k commented Sep 1, 2023

@YJDoc2 I forgot about it 🤦‍♂May I ask you to do it? But it is not rushing because we can update it after releasing v0.2.0

Changes that will occur for properly running in rootless mode : TODO (@YJDoc2)

@YJDoc2
Copy link
Collaborator

YJDoc2 commented Sep 1, 2023

@YJDoc2 I forgot about it 🤦‍♂May I ask you to do it? But it is not rushing because we can update it after releasing v0.2.0

I'll open a PR in few minutes, it is not a big change.

@YJDoc2
Copy link
Collaborator

YJDoc2 commented Sep 1, 2023

@utam0k #2334 👀

Also I think for this PR (releasing 0.2.0) feature label would be more appropriate than cleanup.

@utam0k utam0k added kind/feature and removed kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. labels Sep 1, 2023
@utam0k utam0k merged commit ed75057 into youki-dev:main Sep 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants