Mrugesh Mohapatra

We are officially on Node.js 18 now. We have changed the merge requirements accordingly. You will need to rebase this PR against the main branch OR Click the "Update branch"...

Sort off - the CI flows should be updated only after we have moved all the servers over to v18. This is on my backlog.

I think what we should do is once a user has claimed a certification and then for some reason changed their privacy settings, we should redirect the certification link to...

Ah, right, we should just go ahead and implement the discussion in that thread.

We are officially on Node.js 18 now. We have changed the merge requirements accordingly. You will need to rebase this PR against the main branch OR Click the "Update branch"...

We are officially on Node.js 18 now. We have changed the merge requirements accordingly. You will need to rebase this PR against the main branch OR Click the "Update branch"...

There is a reason we call it the moderator's handbook. We do not have multiple pages for multiple platforms. That is by design. Fragmentation inherently means something parts are less...

We are officially on Node.js 18 now. We have changed the merge requirements accordingly. You will need to rebase this PR against the main branch OR Click the "Update branch"...

We are officially on Node.js 18 now. We have changed the merge requirements accordingly. You will need to rebase this PR against the main branch OR Click the "Update branch"...

Let's get this in to avoid all the conflicts with the lock file. The new API will live in its folder, so we should be OK working on the `main`....