Conversation
This file contains hidden or 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
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.
Upstream release
Bumps bundled fnox binary from 1.23.1 to 1.24.0.
Release: https://github.com/jdx/fnox/releases/tag/v1.24.0
Release notes
A focused release that adds a new
github-oauthlease backend for minting short-lived, user-attributed GitHub tokens via OAuth device flow — without distributing an app private key.Added
github-oauthlease backend (#464) -- @jdxA new lease type that creates GitHub App user access tokens using the OAuth device flow and injects them as
GITHUB_TOKEN(or a custom env var) for the duration offnox exec. It is the recommended option for local development and user-attributedgh/ GitHub API usage where you want a short-lived token tied to the signed-in user instead of a long-lived PAT infnox.toml.fnox exec -- gh pr listOn first run, fnox prints a verification URL and user code, optionally opens the URL in your browser, and polls GitHub until you approve the device prompt. Subsequent runs reuse the cached token until it expires.
Highlights of the backend:
github-appbackend remains the right choice for installation tokens in CI.)keyring_cache = falseto force the device flow on every lease.env_var(e.g."GH_TOKEN") and configurableauth_base/api_basefor GitHub Enterprise Server.open_browsercontrols whether fnox tries to launch the verification URL automatically (usesopen/xdg-open/start).The supported-backends table in the leases guide is updated, and the
github-appdocs now point local/user-attributed workflows atgithub-oauth. See the GitHub OAuth lease docs for the full reference.Full Changelog: jdx/fnox@v1.23.1...v1.24.0
💚 Sponsor fnox
fnox is maintained by @jdx under en.dev — a small independent studio building developer tooling like mise, aube, hk, and more. Keeping fnox secure, maintained, and free is funded by sponsors.
If fnox is handling secrets or config for you or your team, please consider sponsoring at en.dev. Sponsorships are what let fnox stay independent and the project keep moving.