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

support timezone: 0.9.0 #437

Closed
2 tasks done
IVLIVS-III opened this issue Sep 17, 2022 · 3 comments
Closed
2 tasks done

support timezone: 0.9.0 #437

IVLIVS-III opened this issue Sep 17, 2022 · 3 comments

Comments

@IVLIVS-III
Copy link
Contributor

IVLIVS-III commented Sep 17, 2022

Issue description

The timezone dependency is available in version 0.9.0 but cannot be used in projects that depend on device_calendar: 4.2.0 because device_calendar depends on timezone: ^0.8.0.
Due to timezone being a 0.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

  • ensure device_calendar is compatible with timezone: 0.9.0. Compatibility should be given as long as device_calendar does not depend on named database files in package:timezone/data (for example, package:timezone/data/2021e.tzf), since the removal of those named files was the only breaking change from timezone: 0.8.x to 0.9.0.
  • update the timezone dependency in pubspec.yaml to timezone: ^0.9.0
@vixez
Copy link

vixez commented Sep 20, 2022

I created a fork here meanwhile with a version bump. As I needed it for other packages

  device_calendar:
    git:
      url: https://github.com/vixez/device_calendar.git
      ref: develop

@thomassth
Copy link
Contributor

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.

@IVLIVS-III
Copy link
Contributor Author

@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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants