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
Add support for YubiKey OTP codes during release #43863
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This patch adds support for automatically getting OTP codes from your YubiKey during release. You must have the `ykman` commandline tool installed, and have two accounts setup with the names `rubygems.org` and `npmjs.com`. For example, the output from `ykman oath accounts list` on my machine is this: ``` $ ykman oath accounts list npmjs.com:aaron.patterson@gmail.com rubygems.org:aaron.patterson@gmail.com ``` If you meet these conditions, you can do `rake release` without typing an OTP code for every gem. If no `ykman` tool is found on your system, this will just fall back to asking for an OTP code.
I wrote a blog post on setting up |
tenderlove
added a commit
that referenced
this pull request
Dec 14, 2021
Add support for YubiKey OTP codes during release
tenderlove
added a commit
that referenced
this pull request
Dec 14, 2021
Add support for YubiKey OTP codes during release
tenderlove
added a commit
that referenced
this pull request
Dec 14, 2021
Add support for YubiKey OTP codes during release
tenderlove
added a commit
that referenced
this pull request
Feb 11, 2022
Add support for YubiKey OTP codes during release
tenderlove
added a commit
that referenced
this pull request
Feb 11, 2022
* 5-2-sec: Merge pull request #43863 from rails/yubikey-support Preparing for 5.2.6.1 release Preparing for release ActionDispatch::Executor don't fully trust `body#close`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch adds support for automatically getting OTP codes from your
YubiKey during release. You must have the
ykman
commandline toolinstalled, and have two accounts setup with the names
rubygems.org
andnpmjs.com
. For example, the output fromykman oath accounts list
onmy machine is this:
If you meet these conditions, you can do
rake release
without typingan OTP code for every gem.
If no
ykman
tool is found on your system, this will just fall back toasking for an OTP code.