Skip to content

Commit 83fba52

Browse files
committed
latest
1 parent 2ed080c commit 83fba52

File tree

4 files changed

+15
-9
lines changed

4 files changed

+15
-9
lines changed

assets/img/blog/blog-11.png

48.5 KB
Loading

assets/img/blog/blog-6.png

-4.37 KB
Loading

assets/img/blog/blog-7.jpg

-219 KB
Loading

blog/_posts/2025-12-11-rotate-npm-tokens-with-dotenvx-ops.md

Lines changed: 15 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -171,25 +171,31 @@ npm:
171171

172172
#### Step 3
173173

174-
Last, we set `DOTENVX_OPS_TOKEN` in <a href="https://github.com/username/project/settings/secrets/actions">GitHub Actions Secrets</a>.
174+
Last, we set `DOTENVX_OPS_TOKEN` in <a href="https://github.com/username/project/settings/secrets/actions">GitHub Actions Secrets</a> (or GitLab CI, CircleCI, or wherever you run your automated npm publishing).
175175

176176
<img src="https://github.com/user-attachments/assets/db12882b-8b35-40db-a62f-238df32ff3f6" />
177177

178-
Tip: you can find your `DOTENVX_OPS_TOKEN` at <a href="https://ops.dotenvx.com/settings">/settings</a> page.
178+
Tip: Find your `DOTENVX_OPS_TOKEN` on your <a href="https://ops.dotenvx.com/settings">Dotenvx Settings Page</a>.
179179

180180
<img src="https://github.com/user-attachments/assets/df4f6146-5cf9-44a7-9a22-b967d675f3d8" />
181181

182-
That's it!
182+
On your next CI run, it will inject the latest rotated NPM token and successfully publish your npm module(s).
183183

184-
Now publishing is automated with rotating NPM tokens.
184+
<img src="https://github.com/user-attachments/assets/7a201f23-c255-4d75-a46e-326ddf22f0d9" />
185185

186-
- NPM token leaked? Just rotate it - all your operations still work.
187-
- NPM token should be rotated every N days for compliance? Put it on a schedule - all your operations still work.
188-
- Changed an employee who had access to the old token? Rotate it — all your operations still work.
186+
Incredible!
189187

190-
This has been a great setup for us. We publish a lot of npm packages, and ROTs finally made token rotation feel simple again.
188+
## Conclusion
191189

192-
If you're dealing with npm token rotation today, you can start using this immediately by signing up for <a href="https://dotenvx.com/ops">Dotenvx Ops</a>. And if you're running this at enterprise scale — with compliance requirements, scheduled rotation, or broader CI/CD concerns — <a href="mailto:[email protected]">get in touch</a>. We'd like to help.
190+
Publishing now works indefinitely with rotating NPM tokens, powered by a new rotation primitive (ROTs) and passcard connectors.
191+
192+
- *NPM token leaked?* Just rotate it - all your operations still work.
193+
- *NPM token should be rotated every N days for compliance?* Put it on a schedule - all your operations still work.
194+
- *Employee left the company who had access to the old token?* Rotate it - all your operations still work.
195+
196+
This has worked really well for us. If it sounds useful, you can use it too. Sign up for <a href="https://dotenvx.com/ops">Dotenvx Ops</a>.
197+
198+
> P.S. If you're running this at enterprise scale with compliance requirements, scheduled rotation, or broader CI/CD concerns, please <a href="mailto:[email protected]">get in touch</a>. We'd like to help.
193199

194200
---
195201

0 commit comments

Comments
 (0)