GeezerVison

What

Bumps the workspace version 3.2.0 → 3.3.0 (a minor bump) so the new inline OpenVEX generation on apply/scan (--vex <path>) feature — already staged under ## [Unreleased] in CHANGELOG.md — can be released.

There's no automatic version computation in this repo: the Release workflow only reads the version from Cargo.toml, so the bump has to land on main first.

Changes

Generated via scripts/version-sync.sh 3.3.0 (+ Cargo.lock update):

• Cargo.toml — [workspace.package] version and the =3.3.0 socket-patch-core dep pin
• Cargo.lock — socket-patch-cli / socket-patch-core
• npm: main package + 14 platform shims + package-lock.json
• pypi/socket-patch/pyproject.toml

No source/behavior changes — version strings only.

Release steps (after merge)

1. Dispatch the Release workflow. It reads 3.3.0, confirms no v3.3.0 tag exists, and that ## [Unreleased] is non-empty.
2. After publish, rollover-changelog.sh stamps ## [Unreleased] → ## [3.3.0] — <date> automatically.

Note: the v3.2.0 tag isn't present in the local clone (only v3.1.0) — worth a git fetch --tags to confirm before dispatching, since the tag-existence check runs against the CI checkout's view.

🤖 Generated with Claude Code