Skip to content

Commit 6e1d858

Browse files
committed
chore: prepare 0.2.2 release
1 parent e3fde1e commit 6e1d858

21 files changed

Lines changed: 65 additions & 61 deletions

File tree

.github/workflows/release-node.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,9 @@ on:
66
workflow_dispatch:
77
inputs:
88
tag_name:
9-
description: 'Tag name to publish (e.g. v0.2.1) — used for version sync'
9+
description: 'Tag name to publish (e.g. v0.2.2) — used for version sync'
1010
required: true
11-
default: 'v0.2.1'
11+
default: 'v0.2.2'
1212

1313
permissions:
1414
contents: read

.github/workflows/release-wasm.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,9 @@ on:
66
workflow_dispatch:
77
inputs:
88
tag_name:
9-
description: 'Tag name to publish (e.g. v0.2.1) — used for version sync'
9+
description: 'Tag name to publish (e.g. v0.2.2) — used for version sync'
1010
required: true
11-
default: 'v0.2.1'
11+
default: 'v0.2.2'
1212

1313
permissions:
1414
contents: write

CHANGELOG.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,23 @@ this project adheres to [Semantic Versioning](https://semver.org/).
77

88
---
99

10+
## [0.2.2] — 2026-03-26
11+
12+
### Added
13+
- Separate benchmark groups for `non-ocr` and `hybrid` runs so published comparisons can be reported more cleanly
14+
- Shared benchmark snapshot data for the site so landing and docs stay aligned from one source
15+
16+
### Changed
17+
- Bumped the workspace and published SDK manifests to `0.2.2`
18+
- Rebuilt the checked-in WASM package used by the demo and site so browser deployments use the latest parser bundle
19+
- Updated the site/demo release path to ship the refreshed WASM bundle and current benchmark documentation
20+
21+
### Fixed
22+
- Disabled WASM npm publication while keeping the release tarball attached to GitHub Releases
23+
- Corrected benchmark runner/docs grouping so hybrid engines no longer appear under the non-OCR bucket
24+
25+
---
26+
1027
## [0.2.1] — 2026-03-26
1128

1229
### Added

Cargo.lock

Lines changed: 5 additions & 5 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ default-members = [
1515
]
1616

1717
[workspace.package]
18-
version = "0.2.1"
18+
version = "0.2.2"
1919
edition = "2021"
2020
rust-version = "1.85"
2121
license = "Apache-2.0"

crates/edgeparse-cli/Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ name = "edgeparse"
1616
path = "src/main.rs"
1717

1818
[dependencies]
19-
edgeparse-core = { path = "../edgeparse-core", version = "0.2.1" }
19+
edgeparse-core = { path = "../edgeparse-core", version = "0.2.2" }
2020
clap = { workspace = true }
2121
serde = { workspace = true }
2222
serde_json = { workspace = true }
166 KB
Binary file not shown.

crates/edgeparse-wasm/pkg/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
"name": "edgeparse-wasm",
33
"type": "module",
44
"description": "EdgeParse PDF parser — WebAssembly build for browsers",
5-
"version": "0.2.1",
5+
"version": "0.2.2",
66
"license": "Apache-2.0",
77
"homepage": "https://edgeparse.io/docs/api/wasm/",
88
"repository": {

demo/package-lock.json

Lines changed: 2 additions & 2 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

docs/07-cicd-publishing.md

Lines changed: 10 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -12,16 +12,16 @@ Publishing is driven by six GitHub Actions workflows, all triggered by pushing a
1212
semantic version tag:
1313

1414
```bash
15-
git tag v0.2.1
16-
git push origin v0.2.1
15+
git tag v0.2.2
16+
git push origin v0.2.2
1717
```
1818

1919
```text
2020
vX.Y.Z tag
2121
├─ release-rust.yml -> crates.io (pdf-cos, edgeparse-core, edgeparse-cli)
2222
├─ release-python.yml -> PyPI (edgeparse wheels + sdist)
2323
├─ release-node.yml -> npm (edgeparse + 5 platform packages)
24-
├─ release-wasm.yml -> npm (edgeparse-wasm)
24+
├─ release-wasm.yml -> GitHub Releases (edgeparse-wasm tarball)
2525
├─ release-cli.yml -> GitHub Releases (5 CLI archives) + Homebrew tap
2626
└─ release-docker.yml -> GHCR + Docker Hub (linux/amd64, linux/arm64)
2727
```
@@ -51,7 +51,6 @@ Shared verification happens in `ci.yml` on pushes and pull requests:
5151
| npm | `edgeparse-linux-arm64-gnu` | https://www.npmjs.com/package/edgeparse-linux-arm64-gnu |
5252
| npm | `edgeparse-linux-x64-gnu` | https://www.npmjs.com/package/edgeparse-linux-x64-gnu |
5353
| npm | `edgeparse-win32-x64-msvc` | https://www.npmjs.com/package/edgeparse-win32-x64-msvc |
54-
| npm | `edgeparse-wasm` | https://www.npmjs.com/package/edgeparse-wasm |
5554
| GitHub Releases | CLI archives + WASM npm tarball | https://github.com/raphaelmansuy/edgeparse/releases |
5655
| Homebrew | `raphaelmansuy/edgeparse` tap | https://github.com/raphaelmansuy/homebrew-edgeparse |
5756
| GHCR | `ghcr.io/raphaelmansuy/edgeparse` | https://github.com/raphaelmansuy/edgeparse/pkgs/container/edgeparse |
@@ -89,22 +88,22 @@ Each GitHub Release includes:
8988
| Secret | Used by | Purpose |
9089
|--------|---------|---------|
9190
| `CARGO_REGISTRY_TOKEN` | `release-rust.yml` | Publish crates to crates.io |
92-
| `NPM_TOKEN` | `release-node.yml`, `release-wasm.yml` | Publish Node.js and WASM packages to npm |
91+
| `NPM_TOKEN` | `release-node.yml` | Publish Node.js packages to npm |
9392
| `DOCKERHUB_TOKEN` | `release-docker.yml` | Push Docker images to Docker Hub |
9493
| `HOMEBREW_TAP_TOKEN` | `release-cli.yml` | Push `edgeparse.rb` to the Homebrew tap |
9594

9695
### GitHub environments
9796

9897
| Environment | Used by | Notes |
9998
|-------------|---------|-------|
100-
| `npm` | `release-node.yml`, `release-wasm.yml` | Optional protection rules for npm publish jobs |
99+
| `npm` | `release-node.yml`, `release-wasm.yml` | Optional protection rules for npm release jobs |
101100
| `pypi` | `release-python.yml` | Required for PyPI Trusted Publishing |
102101

103102
### External setup
104103

105104
- crates.io: create a token with `publish-new` and `publish-update`
106-
- npm: use a Classic Automation token so the main package, platform packages,
107-
and `edgeparse-wasm` can all publish from CI
105+
- npm: use a Classic Automation token so the main package and platform packages
106+
can publish from CI
108107
- PyPI: configure Trusted Publishing for `release-python.yml` in environment
109108
`pypi`
110109
- Docker Hub: create a read/write access token for account `rmansuy`
@@ -178,7 +177,7 @@ make publish-brew-dry
178177
```bash
179178
# 1. Commit and push the release-prep branch
180179
git add -A
181-
git commit -m "chore: prepare 0.2.1 release"
180+
git commit -m "chore: prepare 0.2.2 release"
182181
git push origin <branch>
183182

184183
# 2. Open and merge the PR
@@ -188,8 +187,8 @@ gh pr merge <pr-number> --merge --delete-branch=false
188187
# 3. Tag the merge commit on main
189188
git checkout main
190189
git pull --ff-only origin main
191-
git tag v0.2.1
192-
git push origin v0.2.1
190+
git tag v0.2.2
191+
git push origin v0.2.2
193192
```
194193

195194
The tag must match `v[0-9]+.[0-9]+.[0-9]+`. The Rust and WASM release

0 commit comments

Comments
 (0)