-
Notifications
You must be signed in to change notification settings - Fork 398
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
Changes for v3 #232
Comments
Closed
Closed
Am going to move forward with this so we can add a go.mod file. I think I'll forgo the context and oauth2 import changes. |
Hmm, some issues with the v3 path. Investigating
Edit: figured it out
|
This was referenced Jul 17, 2020
Okay I think we're at the point we can tag v3. Going to send a README update then call it done. |
README PR sent (#232). Once that's in, I'll tag v3.0.0 and change the default branch to v3. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since we need to modify the import path to make a go.mod work (#230), it might be a good chance to fix some APIs and call it v3.
Some changes that seem uncontroversial:
Changes that are more intrusive:
The text was updated successfully, but these errors were encountered: