yeah that’s frustrating - the portal’s email validation can be picky sometimes. a few things to check:
1. **npm profile email vs package.json** - make sure your `package.json` has the exact same email in the `“author”` field. sometimes it’s formatted differently (like `“author”: “Your Name [email protected]”` vs just the email). try matching it exactly to what’s in your npm profile.
2. **npm cache issue** - the portal might be hitting a cached version. try updating your package version, republishing to npm, then waiting a few mins before submitting to the portal again.
3. **contact n8n directly** - if those don’t work, hit up the n8n team through their support or the discord community. this specific error sometimes needs a manual fix on their end, especially if everything checks out on your side like it does here.