Skip to content

Conversation

@jcyling
Copy link
Contributor

@jcyling jcyling commented Nov 21, 2025

  • All new/changed/fixed functionality is covered by tests (or N/A)
  • I have added documentation for all new/changed functionality (or N/A)

📋 Changes

Updates the V4 migration guide to add documentation for #2159. The noContentProfileResponseWhenUnauthenticated option allows the V4 profile endpoint to replicate V3 behaviour and return a 204 when logged out instead of a 401 error.

📎 References

#2159

@jcyling jcyling requested a review from a team as a code owner November 21, 2025 16:06
@jcyling jcyling changed the title Document noContentProfileResponseWhenUnauthenticated option in V4 migration guide docs: Document noContentProfileResponseWhenUnauthenticated option in V4 migration guide Nov 21, 2025
@frederikprijck
Copy link
Member

Thank you so much for adding this, and apologies for taking so long to get your change in.

@frederikprijck frederikprijck enabled auto-merge (squash) December 12, 2025 08:29
@codecov-commenter
Copy link

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.99%. Comparing base (7b39df2) to head (18e3412).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2431   +/-   ##
=======================================
  Coverage   90.99%   90.99%           
=======================================
  Files          39       39           
  Lines        4520     4520           
  Branches      939      939           
=======================================
  Hits         4113     4113           
  Misses        401      401           
  Partials        6        6           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@frederikprijck
Copy link
Member

frederikprijck commented Dec 12, 2025

We do require commits to be signed in order to merge this PR. Any chance you could sign your commit @jcyling ?

Learn how to sign and verify commits

@tusharpandey13
Copy link
Contributor

Hi @jcyling, we have a requirement that PR commits must have verified signatures. Can you sign your commit cce8df4a223b4b12b851ad243cb7681ce77e68b8 so that we can merge this?

@jcyling jcyling force-pushed the v4-migration-profile-no-content-option branch from 9e00f89 to da567f3 Compare December 15, 2025 12:16
@jcyling
Copy link
Contributor Author

jcyling commented Dec 15, 2025

@frederikprijck @tusharpandey13 Appreciate the review! The commits in this PR are signed. If you prefer a cleaner history, I’m happy to rebase to remove the duplicate commits - let me know.

@tusharpandey13
Copy link
Contributor

I think that looks good, we can use squash and merge for this PR.

@tusharpandey13 tusharpandey13 merged commit 89a2cdf into auth0:main Dec 15, 2025
1 check passed
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.

4 participants