Skip to content

Commit e267443

Browse files
authored
Remove release process section from README
Removed detailed release process instructions from README.
1 parent ee350f9 commit e267443

1 file changed

Lines changed: 0 additions & 31 deletions

File tree

README.md

Lines changed: 0 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -49,35 +49,4 @@ export default [
4949

5050
- [sort-keys-shorthand/sort-keys-shorthand](docs/rules/sort-keys-shorthand.md): extended rule with shorthand support
5151

52-
## Release Process
53-
54-
This project uses [npm trusted publishing](https://docs.npmjs.com/trusted-publishers) with OIDC. Provenance attestations are generated automatically — no npm tokens are needed for publishing.
55-
56-
### One-time setup
57-
58-
These steps only need to be done once, before the first trusted publishing release.
59-
60-
1. **Configure trusted publisher on npmjs.com**
61-
- Go to [package settings](https://www.npmjs.com/package/eslint-plugin-sort-keys-shorthand/access)
62-
- Under **Trusted Publisher**, select **GitHub Actions**
63-
- Set: org/user = `fxOne`, repo = `eslint-plugin-sort-keys-shorthand`, workflow = `release.yml`
64-
- Save
65-
66-
2. **Lock down token access** (recommended)
67-
- On the same page under **Publishing access**, select **"Require two-factor authentication and disallow tokens"**
68-
69-
3. **Clean up old secrets**
70-
- Delete the `NPM_TOKEN` secret from [GitHub repo settings](https://github.com/fxOne/eslint-plugin-sort-keys-shorthand/settings/secrets/actions)
71-
- Optionally delete `AUTOMERGE_TOKEN` as well
72-
- Revoke old automation tokens on [npmjs.com](https://www.npmjs.com/settings/~/tokens)
73-
74-
### Publishing a release
75-
76-
```bash
77-
git checkout master
78-
git pull origin master
79-
git tag v<version>
80-
git push origin v<version>
81-
```
82-
8352
Pushing a `v*` tag triggers the release workflow, which runs tests, publishes to npm with provenance, and creates a GitHub Release.

0 commit comments

Comments
 (0)