Skip to content

feat: add agent email login for CON-1115 - #654

Merged
KAJdev merged 4 commits into
mainfrom
zeke/con-1115-add-agent-flag-to-runpod-python-login-command
Oct 28, 2026
Merged

KAJdev merged 4 commits into
mainfrom
zeke/con-1115-add-agent-flag-to-runpod-python-login-command

Conversation

@KAJdev

@KAJdev KAJdev commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

Adds runpod login --agent --email for headless authentication through the REST signup API. Email verification is bound to the initiating process with PKCE, and the issued API key is saved to the selected credential profile without printing the code or key.

Requires signup authentication attempts to be enabled on the API deployment. Accounts with SSO, MFA, or organization membership use console sign-in and direct API-key login.

Closes CON-1115.

Comment thread runpod/apps/auth.py Resolved
Comment thread runpod/rp_cli/main.py Resolved
@KAJdev
KAJdev merged commit 7766b9b into main Oct 28, 2026
10 checks passed
@KAJdev
KAJdev deleted the zeke/con-1115-add-agent-flag-to-runpod-python-login-command branch October 28, 2026 19:51
deanq added a commit that referenced this pull request Nov 10, 2026
Release PR #594 cut 2.0.0 but wrote its section as [2.1.0] with a
compare link to a v2.1.0 tag that does not exist. It also omitted the
breaking apps SDK change and everything released in the 2.0.0 rcs.

- Retitle the section to 2.0.0, compare v1.12.0...v2.0.0, dated
  2026-10-30 (the tag and GitHub release date)
- Add a BREAKING CHANGES entry for #534
- Add the feat/fix/perf commits since 1.12.0 that the section missed,
  including #654 and #658 merged after the release PR was opened
- Fold the hand-written "Unreleased" notes into 2.0.0; that code ships
  in the v2.0.0 tag, and release-please would otherwise insert future
  sections above it
deanq added a commit that referenced this pull request Nov 10, 2026
Release PR #594 cut 2.0.0 but wrote its section as [2.1.0] with a
compare link to a v2.1.0 tag that does not exist. It also omitted the
breaking apps SDK change and everything released in the 2.0.0 rcs.

- Retitle the section to 2.0.0, compare v1.12.0...v2.0.0, dated
  2026-10-30 (the tag and GitHub release date)
- Add a BREAKING CHANGES entry for #534
- Add the feat/fix/perf commits since 1.12.0 that the section missed,
  including #654 and #658 merged after the release PR was opened
- Fold the hand-written "Unreleased" notes into 2.0.0; that code ships
  in the v2.0.0 tag, and release-please would otherwise insert future
  sections above it
deanq added a commit that referenced this pull request Nov 10, 2026
Release PR #594 cut 2.0.0 but wrote its section as [2.1.0] with a
compare link to a v2.1.0 tag that does not exist. It also omitted the
breaking apps SDK change and everything released in the 2.0.0 rcs.

- Retitle the section to 2.0.0, compare v1.12.0...v2.0.0, dated
  2026-10-30 (the tag and GitHub release date)
- Add a BREAKING CHANGES entry for #534
- Add the feat/fix/perf commits since 1.12.0 that the section missed,
  including #654 and #658 merged after the release PR was opened
- Fold the hand-written "Unreleased" notes into 2.0.0; that code ships
  in the v2.0.0 tag, and release-please would otherwise insert future
  sections above it
deanq added a commit that referenced this pull request Nov 11, 2026
Release PR #594 cut 2.0.0 but wrote its section as [2.1.0] with a
compare link to a v2.1.0 tag that does not exist. It also omitted the
breaking apps SDK change and everything released in the 2.0.0 rcs.

- Retitle the section to 2.0.0, compare v1.12.0...v2.0.0, dated
  2026-10-30 (the tag and GitHub release date)
- Add a BREAKING CHANGES entry for #534
- Add the feat/fix/perf commits since 1.12.0 that the section missed,
  including #654 and #658 merged after the release PR was opened
- Fold the hand-written "Unreleased" notes into 2.0.0; that code ships
  in the v2.0.0 tag, and release-please would otherwise insert future
  sections above it
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