EnvGap
Configure "Trusted Publishing" in npmjs.com
envgap__lint-staged__lint-staged-1641
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- In a clean container the reported failure did not reproduce, or the known fix did not make the project run.
02 / ENVIRONMENT RECIPE
- Base commit
b320abd1e9e3c7d84d0839945993675dd55545fe- Manifest
package.json- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
lint-staged/lint-staged #1641 · read the original issue
Hello @okonet, I would be interested in trying out this new option for publishing `lint-staged` to npmjs.com, called _Trusted Publishing_. Supposedly with it, we could remove your npm access token from the CI secrets, and have it work automagically instead: <img width="320" height="298" alt="Image" src="https://github.com/user-attachments/assets/704057e4-33c2-41d8-a6cc-9509191fcb9a" /> I was also wondering if after over 5 years of maintaining, you'd be willing to invite me as maintainer to the npm package directly so that I can check this configuration myself: <img width="320" height="87" alt="Image" src="https://github.com/user-attachments/assets/da6b1e07-2fc2-4447-a8c8-25c77c7e942c" />
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]