You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: blog/_posts/2025-12-11-rotate-npm-tokens-with-dotenvx-ops.md
+15-9Lines changed: 15 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -171,25 +171,31 @@ npm:
171
171
172
172
#### Step 3
173
173
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).
- 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!
189
187
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
191
189
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.
0 commit comments