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

release v2023.12.0 + email auth #66

Merged
merged 4 commits into from
Dec 5, 2023
Merged

release v2023.12.0 + email auth #66

merged 4 commits into from
Dec 5, 2023

Conversation

andrewkmin
Copy link
Contributor

No description provided.

Copy link

vercel bot commented Dec 4, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview 2 resolved Dec 5, 2023 11:59pm

@andrewkmin andrewkmin changed the title Release/v2023.12.0 release v2023.12.0 + email auth Dec 5, 2023
| Invitations | 100 |
| Tags | 100 |
| Authenticators per user | 10 |
| API keys per user (long-lived) | 10 |
Copy link
Contributor Author

Choose a reason for hiding this comment

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

is this clear enough? or should we further explain the difference between long-lived and expiring?

@@ -54,6 +54,8 @@ Navigate to your user page by clicking on "User Details" in the user dropdown me

Click on "Create API keys" and follow the prompts to add the generated public API key. You'll be required to authenticate with the same authenticator used during onboarding. After this succeeds, you should be all set to interact with our API.

NOTE: if you would like to manually your locally stored public/private API key files (e.g. `key.public`, `key.private`), you will have to save the files without newlines (which occupy extra bytes). For example, for VIM, use `:set binary noeol` or `:set binary noendofline` before writing.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

note on usability: this currently only affects api keys created via CLI (api keys created via dashboard app are saved as json files). but this matters if users are trying to manually copy/paste their api key credentials into local files, in which case they'll have to get rid of newline characters.

@andrewkmin andrewkmin merged commit cbc26f0 into main Dec 5, 2023
4 checks passed
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.

2 participants