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

mv lifecycle to stand-alone directory #5425

Open
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

ghostloda
Copy link
Collaborator

mv lifecycle to stand-alone directory

@sealos-ci-robot
Copy link
Member

sealos-ci-robot commented Feb 27, 2025

🤖 Generated by lychee action

Summary

Status Count
🔍 Total 2082
✅ Successful 464
⏳ Timeouts 0
🔀 Redirected 0
👻 Excluded 1616
❓ Unknown 0
🚫 Errors 0

Full action output

Full Github Actions output

Copy link

codecov bot commented Feb 28, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 61.97%. Comparing base (6718151) to head (a0af435).
Report is 7 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5425   +/-   ##
=======================================
  Coverage   61.97%   61.97%           
=======================================
  Files           8        8           
  Lines         647      647           
=======================================
  Hits          401      401           
  Misses        200      200           
  Partials       46       46           

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

Signed-off-by: ghostloda <[email protected]>

fix workflows
Signed-off-by: ghostloda <[email protected]>
Signed-off-by: ghostloda <[email protected]>
@zzjin zzjin added this to the v5.0 milestone Feb 28, 2025
@zzjin
Copy link
Collaborator

zzjin commented Feb 28, 2025

You also need to adjust root dir's go.work(may be go.mod,go.sumis need move to lifecircle too,) to match new structure.

@fanux
Copy link
Member

fanux commented Feb 28, 2025

It can be placed in a separate directory and maintained independently. Just ensure version compatibility in subsequent iterations. Higher versions of Sealos should be compatible with the installation of the latest five major versions of Kubernetes.

Signed-off-by: ghostloda <[email protected]>
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