Skip to content

Commit fa4c85d

Browse files
committed
init
1 parent a62b66d commit fa4c85d

2 files changed

Lines changed: 12 additions & 10 deletions

File tree

.github/workflows/publish.yml

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,11 @@ jobs:
2626

2727
- name: Install dependencies
2828
run: npm ci
29+
30+
- name: Set version from tag
31+
run: |
32+
VERSION=${GITHUB_REF#refs/tags/v}
33+
npm version "$VERSION" --no-git-tag-version --allow-same-version
2934
3035
- name: Build package
3136
run: npm run build
@@ -64,8 +69,6 @@ jobs:
6469
## Changes in this release
6570
6671
${{ env.CHANGES }}
67-
68-
For full details, see the [CHANGELOG](https://github.com/lightfeed/extractor/blob/main/CHANGELOG.md).
6972
draft: false
7073
prerelease: false
7174

CONTRIBUTING.md

Lines changed: 7 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -32,16 +32,15 @@ The workflow includes:
3232

3333
## Release Process (Maintainers)
3434

35-
This project uses semantic versioning. To create a new release:
35+
This project uses semantic versioning. To create a new release, tag `main` and push:
3636

3737
```bash
38-
npm version patch # or minor, or major
39-
git push origin main --tags
38+
git tag v0.5.0
39+
git push origin v0.5.0
4040
```
4141

42-
`npm version` automatically bumps the version in `package.json` and `package-lock.json`, creates a commit, and creates a git tag.
43-
4442
When the tag is pushed, GitHub Actions will automatically:
45-
1. Build the package and run tests
46-
2. Create a GitHub Release with notes generated from git history
47-
3. Publish the package to npm
43+
1. Set the version in `package.json` from the tag
44+
2. Build the package and run tests
45+
3. Create a GitHub Release with notes generated from git history
46+
4. Publish the package to npm

0 commit comments

Comments
 (0)