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

Backport security fixes and dependency updates to v1 (v1-edge) #546

Merged
merged 7 commits into from
Dec 17, 2024

Conversation

masnax
Copy link
Contributor

@masnax masnax commented Dec 13, 2024

No description provided.

@masnax masnax requested a review from tomponline as a code owner December 13, 2024 06:36
@masnax masnax marked this pull request as draft December 13, 2024 07:07
@masnax masnax force-pushed the v1-edge branch 3 times, most recently from 76c1b69 to c760b08 Compare December 16, 2024 16:29
@masnax masnax changed the title Backport security fixes and dependency updates to v1 Backport security fixes and dependency updates to v1 (v1-edge) Dec 16, 2024
@masnax masnax force-pushed the v1-edge branch 6 times, most recently from 28f4b03 to 62beeb7 Compare December 17, 2024 00:34
cmd/microcloud: Force disk ordering by path name

(cherry picked from commit 359cd46)
Signed-off-by: Max Asnaashari <[email protected]>
@masnax masnax marked this pull request as ready for review December 17, 2024 02:47
@masnax masnax requested a review from roosterfish December 17, 2024 05:51
Copy link
Contributor

@roosterfish roosterfish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some of the commits don't allow tracing back the original change/commit. Can you use cherry-pick -x for them?

@masnax
Copy link
Contributor Author

masnax commented Dec 17, 2024

Some of the commits don't allow tracing back the original change/commit. Can you use cherry-pick -x for them?

Tracking with cherry picks wouldn't be all that easy here because we're taking bits and pieces that have been iterated on for a year. I can cherry pick the last commit that is "thematically similar" but since we're closing this branch by mid-year, I don't think it would be all that helpful.

Copy link
Contributor

@roosterfish roosterfish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, fine for me!

@masnax masnax merged commit 9b6555e into canonical:v1-edge Dec 17, 2024
16 of 17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants