When using ATP_IDENTIFIER and ATP_APP_PASSWORD without PDS_URL for app-password authentication in CI/CD workflows, Sequoia falls back to https://bsky.social instead of resolving the user's PDS from the identifier/DID.
The documentation states that the custom PDS URL is optional and auto-resolved. However, self-hosted PDS users currently need to set PDS_URL explicitly.
The fallback behavior appears to be defined here: https://tangled.org/stevedylan.dev/sequoia/blob/85e63d5883f70eab5ed9d5f55762fbe4b6831f39/packages/cli/src/lib/credentials.ts#L140
At the very least we should update docs to say that
PDS_URLis required for self-hosting. But it does seem that resolving the DID and then the PDS is possible with an app password. I mean, not only doesgoatdo it but it'd have to to be useful. Maybe instead of simply assumingbluesky.social, if$PDS_URLis not defined we first attempt to resolve the DID then the PDS or err otherwise. I imagine the point was that most people don't self-host, but with a growing number of self-hosters—especially those seeming to stick with Bluesky—that's no longer a safe enough assumption. @stevedylan.dev what do you think about this proposed change?