Skip to content

Commit a0e5263

Browse files
committed
fix: resolve linting errors in DEVELOPMENT.md
1 parent 0c2d975 commit a0e5263

File tree

1 file changed

+0
-5
lines changed

1 file changed

+0
-5
lines changed

DEVELOPMENT.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -77,13 +77,11 @@ We use GitHub Actions to automate our release process, connecting GitHub Release
7777
```
7878

7979
This will:
80-
8180
- Update the version in package.json
8281
- Create a git tag
8382
- Push the changes and tag to GitHub
8483

8584
2. **Create GitHub Release**:
86-
8785
- Go to GitHub repository → "Releases" → "Draft a new release"
8886
- Choose the tag that was just created
8987
- Fill in release notes detailing what's new, fixes, and any breaking changes
@@ -92,7 +90,6 @@ We use GitHub Actions to automate our release process, connecting GitHub Release
9290
3. **Automated Publishing**:
9391

9492
The GitHub Action will automatically:
95-
9693
- Verify the package version matches the GitHub tag
9794
- Run linting and build checks
9895
- Generate a changelog from commits since the last release
@@ -106,12 +103,10 @@ We use GitHub Actions to automate our release process, connecting GitHub Release
106103
To set up automated publishing:
107104

108105
1. Generate an NPM access token:
109-
110106
- Go to npmjs.com → User Settings → Access Tokens
111107
- Create a new token with "Automation" type and publish permissions
112108

113109
2. Add the token to GitHub repository secrets:
114-
115110
- Go to your GitHub repository → Settings → Secrets → Actions
116111
- Add a new secret named `NPM_TOKEN` with the value of your NPM token
117112

0 commit comments

Comments
 (0)