-
Notifications
You must be signed in to change notification settings - Fork 547
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
Jtmoon79 test yml run publish package #1539
Closed
jtmoon79
wants to merge
252
commits into
chronotope:main
from
jtmoon79:jtmoon79-test_yml_run_publish_package
Closed
Jtmoon79 test yml run publish package #1539
jtmoon79
wants to merge
252
commits into
chronotope:main
from
jtmoon79:jtmoon79-test_yml_run_publish_package
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
Co-authored-by: Dirkjan Ochtman <dirkjan@ochtman.nl>
Co-authored-by: Dirkjan Ochtman <dirkjan@ochtman.nl>
Co-authored-by: Dirkjan Ochtman <dirkjan@ochtman.nl>
….4.x-v3 Add sub days from 0.4.x v3
…ules The internal structs can be moved into their respective modules because `pub(super)` is now supported by the MSRV.
As discussed in chronotope#263. Note that this breaks existing code that did not explicitly specify the offset in calls to `DateTime::parse_from_*`, as they are now ambiguous. Relies on chronotope#271 for conversion back into `DateTime<Utc>` from `DateTime<FixedOffset>` as the latter is used under the hood.
Clarify the behavior of the parse methods, the relationship between ISO 8601 and RFC 3339, and use a brief description on the first line of each function's rustdoc to keep the resulting documentation pretty and concise.
Construct NaiveDateTime from millis since epoch
https://rustsec.org/advisories/RUSTSEC-2021-0127 criterion v0.3 contained an unmaintained crate which seemed to contained another security issue that eas fixed in v0.04. All tests passed.
This file is no longer needed but hasn't yet been deleted
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1539 +/- ##
==========================================
+ Coverage 91.82% 93.96% +2.13%
==========================================
Files 40 37 -3
Lines 18345 16662 -1683
==========================================
- Hits 16846 15656 -1190
+ Misses 1499 1006 -493 ☔ View full report in Codecov by Sentry. |
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.
Run
cargo publish
andcargo package
. Test that they succeed.