Skip to content

feat: add retry support, FedCM login types, and error schemas#841

Open
fern-api[bot] wants to merge 7 commits into
masterfrom
fern-bot/2026-05-18_04-50-14_812
Open

feat: add retry support, FedCM login types, and error schemas#841
fern-api[bot] wants to merge 7 commits into
masterfrom
fern-bot/2026-05-18_04-50-14_812

Conversation

@fern-api
Copy link
Copy Markdown
Contributor

@fern-api fern-api Bot commented May 18, 2026 •
edited by developerkunal
Loading

Changes

  • Added configurable max_retries parameter to Auth0 and AsyncAuth0 clients (defaults to 2 with exponential backoff)
  • New error types: BadRequestSchema, ForbiddenSchema, UnauthorizedSchema, TooManyRequestsSchema
  • New types: FedCmLogin, FedCmLoginGoogle, CredentialDeviceTypeEnum
  • Extended user_authentication_method and resource_server response types with additional fields
  • Updated connection types with additional validation fields
  • Expanded clients, refresh_tokens, resource_servers, tickets, and users/authentication_methods endpoint parameters

Testing

  • Wire tests cover new and updated endpoints

  • CI matrix runs on Python 3.10, 3.11, 3.12, 3.13

  • This change adds unit test coverage

  • This change has been tested on the latest version of the platform/language or why not

Checklist

@fern-api fern-api Bot requested a review from a team as a code owner May 18, 2026 04:50
@fern-api fern-api Bot force-pushed the fern-bot/2026-05-18_04-50-14_812 branch from 099011e to a2e752b Compare May 18, 2026 04:59
fern-api Bot added 2 commits May 18, 2026 05:04
@fern-api
[fern-generated] Update SDK
c1c1814 
Generated by Fern
CLI Version: unknown
Generators:
  - fernapi/fern-python-sdk: 5.12.10
@fern-api
[fern-replay] Applied customizations
ec4257c 
Patches applied (2):
  - patch-f182694f: fix: Add top-level `py.typed` marker to resolve IDE import errors (#829)
  - patch-1026b4d8: Release 5.4.0 (#838)

Patches with unresolved conflicts (1):
  - patch-4894603d: chore: Restore custom wiring in management/__init__.py
    Run `fern-replay resolve` to apply these customizations.

Patches absorbed by generator (1):
  - patch-360322ac: chore: migrate RL scanner to shared devsecops-tooling action (#837)
    The generator now produces these customizations natively.
@fern-api fern-api Bot force-pushed the fern-bot/2026-05-18_04-50-14_812 branch from a2e752b to ec4257c Compare May 18, 2026 05:04
@fern-support fern-support mentioned this pull request May 18, 2026
Merged
@fern-support @tstanmay13
fix: resolve [fern-replay] conflict in management/__init__.py (#842)
1bdc039 
## Summary

Resolves the unresolved \`patch-4894603d\` conflict surfaced by Replay
in #841. Adds one commit on top of \`fern-bot/2026-05-18_04-50-14_812\`
that re-applies the custom wiring in
\`src/auth0/management/__init__.py\` against the new generation output,
and updates \`.fern/replay.lock\` to reflect the resolution.

## What the conflict was

The new generation in #841 added new types (\`BadRequestSchema\`,
\`ForbiddenSchema\`, \`TooManyRequestsSchema\`, \`UnauthorizedSchema\`,
\`FlowsVaultConnectio*\`, \`CredentialDeviceTypeEnum\`) immediately
adjacent to the existing customer wiring entries
(\`AsyncManagementClient\`, \`AsyncTokenProvider\`,
\`ManagementClient\`, \`TokenProvider\`) in \`__init__.py\`'s sorted
\`_dynamic_imports\` dict and \`__all__\` list. The 3-way merge
correctly flagged this as a conflict — both sides added entries to the
same sorted regions.

\`fern replay resolve\` produced 7 conflict-marker regions. All 7 are
purely additive (one side's entries are a strict subset of the other;
the merged result is the union). No same-key replacements, no
overlapping changes.

## Resolution table

| Region | Line | Resolution | Reason |
|---|---|---|---|
| 1 | 84 | Took Generated side | Generator added \`BadRequestSchema\`,
\`BadRequestSchemaError\` |
| 2 | 1834 | Took Generated side | Generator added
\`FlowsVaultConnectio*\` types |
| 3 | 2875 | Took customer side | Preserves
\`AsyncManagementClient\`/\`AsyncTokenProvider\` wiring in
\`_dynamic_imports\` |
| 4 | 2913 | Took Generated side | Generator added
\`BadRequestSchema\`/\`BadRequestSchemaError\` keys |
| 5 | 5667 | Took customer side | Preserves
\`AsyncManagementClient\`/\`AsyncTokenProvider\` wiring in \`__all__\` |
| 6 | 5705 | Took Generated side | Generator added
\`BadRequestSchema\`/\`BadRequestSchemaError\` to \`__all__\` |
| 7 | 7915 | Took customer side | Preserves \`ManagementClient\` in
\`__all__\` |

After resolution, \`fern replay resolve\` Phase 2 finalized the commit
and updated the lockfile.

## Verification

After this PR merges into the \`fern-bot/2026-05-18_04-50-14_812\`
branch:

- All 11 customer-wiring entries are present in
\`src/auth0/management/__init__.py\` (imports, \`_dynamic_imports\`
keys, \`__all__\` entries)
- \`.fern/replay.lock\` no longer has any patch with \`status:
unresolved\` or \`status: resolving\`
- The \`[fern-replay] Resolved conflicts\` commit is classified by the
detector as a generation boundary, so future regens treat it correctly
- The diff vs master is now only the new generator-added types
(legitimate spec evolution), no missing wiring

## Once merged

The bot branch will reflect the resolved state. PR #841 then becomes a
clean merge into \`master\`.

Co-authored-by: Tanmay Singh <tstanmay13@gmail.com>
@developerkunal developerkunal mentioned this pull request May 19, 2026
Merged
5 tasks
developerkunal added a commit that referenced this pull request May 19, 2026
@developerkunal
chore: drop Python 3.9 support, add Python 3.13 (#843)
18f283e 
### Changes

- Drop Python 3.9 from supported versions (EOL since October 2025)
- Add Python 3.13 to the test matrix and classifiers
- Bump minimum Python version to `>=3.10` in `pyproject.toml`
- Update publish workflow to build on Python 3.10
- Unpin Poetry version constraint (Poetry 2.x requires Python 3.10+,
which is now our minimum)

This also fixes CI failures on PR #841 where `pipx install poetry` was
pulling Poetry 2.x which crashes on Python 3.9 with `TypeError:
dataclass() got an unexpected keyword argument 'slots'`.

### References

- [Poetry 2.0
changelog](https://python-poetry.org/blog/announcing-poetry-2.0.0/)
(requires Python 3.10+)
- [Python 3.9 EOL](https://devguide.python.org/versions/) (end-of-life
October 2025)

### Testing

- CI matrix now runs on Python 3.10, 3.11, 3.12, 3.13
- No code changes to the library itself, only build/CI configuration

- [ ] This change adds unit test coverage
- [x] This change has been tested on the latest version of the
platform/language or why not

### Checklist

- [x] I have read the [Auth0 general contribution
guidelines](https://github.com/auth0/open-source-template/blob/master/GENERAL-CONTRIBUTING.md)
- [x] I have read the [Auth0 Code of
Conduct](https://github.com/auth0/open-source-template/blob/master/CODE-OF-CONDUCT.md)
- [x] All existing and new tests complete without errors
developerkunal and others added 4 commits May 19, 2026 17:38
@developerkunal
Merge branch 'master' into fern-bot/2026-05-18_04-50-14_812
a041e2d
@developerkunal
chore: remove client_wrapper.py from .fernignore
357e5d7
@fern-api
SDK regeneration (#844)
da98e49 
Automated SDK generation by Fern

---

✅ Customizations automatically preserved in this update.

---------

Co-authored-by: fern-api <115122769+fern-api[bot]@users.noreply.github.com>
@developerkunal
chore: re-apply Auth0 telemetry customization to regenerated client_w…
9c0c549 
…rapper.py
@developerkunal developerkunal changed the title SDK regeneration feat: add retry support, FedCM login types, and error schemas May 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@fern-support @developerkunal