-
Notifications
You must be signed in to change notification settings - Fork 279
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
support timezone: 0.9.0
#437
Comments
I created a fork here meanwhile with a version bump. As I needed it for other packages
|
Give me a PR and I'll push it through I can't self push without other maintainers' approval, which all seems to be inactive. |
@thomassth PR has been created, thx for your efforts in keeping this plugin alive. |
thomassth
added a commit
that referenced
this issue
Sep 27, 2022
Updated multiple underlying dependencies (closes #437).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue description
The
timezone
dependency is available in version0.9.0
but cannot be used in projects that depend ondevice_calendar: 4.2.0
becausedevice_calendar
depends ontimezone: ^0.8.0
.Due to
timezone
being a0.x.x
version, automatic version solving is treating the change in minor version number as a "breaking change" that is not allowed automatically.Steps to resolve this issue
device_calendar
is compatible withtimezone: 0.9.0
. Compatibility should be given as long asdevice_calendar
does not depend on named database files inpackage:timezone/data
(for example,package:timezone/data/2021e.tzf
), since the removal of those named files was the only breaking change fromtimezone: 0.8.x
to0.9.0
.timezone
dependency inpubspec.yaml
totimezone: ^0.9.0
The text was updated successfully, but these errors were encountered: