-
Notifications
You must be signed in to change notification settings - Fork 834
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
v3.2.1 #3937
Merged
Merged
v3.2.1 #3937
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
Signed-off-by: Patrick Zhao <[email protected]>
Signed-off-by: Patrick Zhao <[email protected]>
PetrusZ
force-pushed
the
ft/release-3.2.1
branch
2 times, most recently
from
January 6, 2025 03:44
1284949
to
bdf1abc
Compare
PetrusZ
force-pushed
the
ft/release-3.2.1
branch
16 times, most recently
from
January 7, 2025 01:58
76dc312
to
c481b7d
Compare
Signed-off-by: Patrick Zhao <[email protected]>
PetrusZ
force-pushed
the
ft/release-3.2.1
branch
from
January 7, 2025 02:24
c481b7d
to
f57ed46
Compare
Signed-off-by: Patrick Zhao <[email protected]>
PetrusZ
force-pushed
the
ft/release-3.2.1
branch
2 times, most recently
from
January 7, 2025 07:52
6d3f7ab
to
2631905
Compare
Signed-off-by: Patrick Zhao <[email protected]>
PetrusZ
force-pushed
the
ft/release-3.2.1
branch
from
January 7, 2025 07:54
2631905
to
febd0b1
Compare
Signed-off-by: Patrick Zhao <[email protected]>
PetrusZ
force-pushed
the
ft/release-3.2.1
branch
8 times, most recently
from
January 8, 2025 08:38
b425417
to
ea3d541
Compare
jamsman94
approved these changes
Jan 8, 2025
Signed-off-by: Patrick Zhao <[email protected]>
PetrusZ
force-pushed
the
ft/release-3.2.1
branch
from
January 8, 2025 08:54
ea3d541
to
b364bd0
Compare
PetrusZ
added a commit
to PetrusZ/zadig
that referenced
this pull request
Jan 8, 2025
* support list release plan by update time Signed-off-by: Patrick Zhao <[email protected]> * add 321 ua Signed-off-by: Patrick Zhao <[email protected]> * update third part cron lib to support year in cron service Signed-off-by: Patrick Zhao <[email protected]> * update 321 ua Signed-off-by: Patrick Zhao <[email protected]> * add sort by update time in list release plan Signed-off-by: Patrick Zhao <[email protected]> * improve code Signed-off-by: Patrick Zhao <[email protected]> * add failback mechanism in case missed schedule time if cron restarted Signed-off-by: Patrick Zhao <[email protected]> --------- Signed-off-by: Patrick Zhao <[email protected]>
5 tasks
jamsman94
pushed a commit
that referenced
this pull request
Jan 8, 2025
* support list release plan by update time * add 321 ua * update third part cron lib to support year in cron service * update 321 ua * add sort by update time in list release plan * improve code * add failback mechanism in case missed schedule time if cron restarted --------- Signed-off-by: Patrick Zhao <[email protected]>
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.
What this PR does / Why we need it:
What is changed and how it works?
Does this PR introduce a user-facing change?