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

Prepare release of v0.8.3 #921

Merged
merged 5 commits into from
Jun 10, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Apply suggestions from code review
  • Loading branch information
philss authored Jun 10, 2024
commit 33602e56238bccb0327c2efc306a17a1eadeb5ea
3 changes: 2 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

## [v0.8.3] - 2024-06-07
## [v0.8.3] - 2024-06-10

### Added

Expand All @@ -22,6 +22,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
The idea is to mirror Elixir's datetime, and introduce support for time zones.
Please note: `{:datetime, precision}` will work as an alias for `{:naive_datetime, precision}` for now but will raise a warning.
The alias will be removed in a future release.
philss marked this conversation as resolved.
Show resolved Hide resolved

- Literal `%NaiveDateTime{}` structs used in expressions will now have `:microsecond` precision.
Previously they defaulted to `:nanosecond` precision.
This was incorrect because `%NaiveDateTime{}` structs only have `:microsecond` precision.
Expand Down
Loading