Implement Update Current User Profile API (Name, etc.)

[thlpkee20-wq]

Description
Implement PATCH /api/users/me for the authenticated user to update their name and other non-sensitive profile fields.

Requirements and context

• Implement only in new files or by extending users route. Use user repository update. Do not modify package.json, src/index.ts. Require JWT.

Suggested execution

• Branch: git checkout -b feature/update-profile-api
• Add PATCH handler and tests. Example commit message: feat(api): add update current user profile

Guidelines

• Additive route only. Timeframe: 96 hours.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[jayjayScript]

@jayjayScript has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I want to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @jayjayScript to this issue.

[drips-wave]

Congratulations, @jayjayScript! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @jayjayScript: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are issued when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[ayomideadeniran]

@ayomideadeniran has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I'm a full-stack developer and I'd like to take this issue.
I understand the requirements and will follow the existing project structure, keep the implementation clean, and include proper tests where applicable.

ETA: 1–3 days (depending on scope)
Portfolio: https://knightsdev-portfolio.vercel.app/

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ayomideadeniran to this issue.

[johnsmccain]

@johnsmccain has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I would like to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @johnsmccain to this issue.

[rosemary21]

@rosemary21 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I can quickly complete it before the deadline
I’d love to work on this issue because it’s a clean, high-impact API improvement that directly enhances user experience while reinforcing proper authentication and data integrity practices. Updating the authenticated user’s profile is a core feature in most applications, and implementing it correctly (especially around JWT validation and restricting updates to non-sensitive fields) is important for both security and maintainability.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @rosemary21 to this issue.

[Jayrodri088]

@Jayrodri088 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I'll create PATCH /api/users/me endpoint in new src/routes/users/profile.ts file allowing authenticated users to update non-sensitive profile fields (name, displayName, avatarUrl, bio, timezone) via JWT middleware. Uses Prisma update() with authenticated userId, validates partial updates via Zod schema (z.object({ name: z.string().min(2).max(50).optional(), ... })), returns 200 { user: { id, name, displayName, avatarUrl, bio, updatedAt } } excluding sensitive data.

Implements idempotency via updatedAt check, rate limiting (10/min per user), and audit logging. Error responses: 400 validation errors, 401 unauthorized, 403 forbidden. Compatible with existing route loader, requires no bootstrap changes. ETA: 2 hours

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Jayrodri088 to this issue.

[Jayrodri088]

@thlpkee20-wq could I take this on quickly before the wave ends

[Jayrodri088]

I think the other person withdrew @thlpkee20-wq

[meshackyaro]

@meshackyaro has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I'll like to work on this issue because I'm familiar with the codebase. Please assign this to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @meshackyaro to this issue.

[nikkybel]

@nikkybel has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Can I be assign this issue?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @nikkybel to this issue.