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

refactor!: use Dart 3 #598

Merged
merged 4 commits into from
Aug 23, 2023
Merged

refactor!: use Dart 3 #598

merged 4 commits into from
Aug 23, 2023

Conversation

Vinzent03
Copy link
Collaborator

This is the first pr to begin working on v2 of our packages.

Where do we want to merge this into? Do we create a new v2 branch and collect all prs there and keep main for v1 or do we do it the other way around?
I would keep the possibility to do fixes to v1 while working on v2.

Changes

  • Make Dart 3 minimum version
  • upgrade lints packages
    • fix new linter warnings
  • upgrade mocktail in realtime_client
  • upgrade dotenv in gotrue

@dshukertjr
Copy link
Member

This is nice! Let's actually create a new next branch, and merge all the changes for v2 there.

@dshukertjr dshukertjr closed this Aug 23, 2023
@Vinzent03 Vinzent03 reopened this Aug 23, 2023
@Vinzent03 Vinzent03 changed the base branch from main to next August 23, 2023 08:31
Copy link
Member

@dshukertjr dshukertjr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. The CI failing is a bit annoying, but it's the dev branch so I'm not too worried.

@Vinzent03
Copy link
Collaborator Author

Yeah that's really strange, I'm trying to reproduce it, but the tests pass with Dart dev and beta.

@Vinzent03 Vinzent03 merged commit 02c4071 into next Aug 23, 2023
22 of 23 checks passed
@Vinzent03 Vinzent03 deleted the refactor/dart3 branch August 23, 2023 09:23
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

Successfully merging this pull request may close these issues.

None yet

2 participants