chore: release v3.1.2

[github-actions]

Automated version bump to 3.1.2 and CHANGELOG update from publish workflow run #322.

[greptile-apps]

Greptile Summary

This is the second automated commit of the v3.1.2 release workflow, updating the three files that are regenerated after the native binaries are built and published to npm — Cargo.toml, generated/DEPENDENCIES.json, and package-lock.json. The first release commit (PR #399) already bumped package.json and updated CHANGELOG.md.

Key changes:

• Cargo.toml version bumped from 3.1.0 → 3.1.2 (the crate was not bumped during the intermediate 3.1.1 npm-only patch release, creating a one-version gap).
• generated/DEPENDENCIES.json cleaned up: the previous ELSPROBLEMS error state caused by stale 3.0.4 linux-x64 binaries is gone now that properly versioned 3.1.2 binaries are published.
• package-lock.json updated from 3.1.1 → 3.1.2 with correct integrity hashes for all six platform packages; libc discriminator fields (glibc/musl) are also added to the three Linux packages, improving npm's platform resolution.

Confidence Score: 4/5

• This PR is safe to merge — it is a routine automated artifact update with no logic changes, only version numbers and generated lockfile content.
• All three files are either generated or auto-bumped by the publish workflow. The integrity hashes are correctly formed, the DEPENDENCIES.json error state is properly resolved, and the platform package updates are consistent. The only minor concern is Cargo.toml skipping version 3.1.1 due to a JS-only patch cycle, which does not affect runtime behavior but is worth noting for versioning hygiene.
• crates/codegraph-core/Cargo.toml — version gap (3.1.0 → 3.1.2, skipping 3.1.1) is worth verifying against the release process.

Important Files Changed

Filename	Overview
crates/codegraph-core/Cargo.toml	Version bumped from 3.1.0 to 3.1.2, skipping 3.1.1 (which was a JS-only npm release where Cargo.toml was not updated). Functionally safe for this release, but creates a versioning gap worth noting.
generated/DEPENDENCIES.json	Version updated to 3.1.2; previous ELSPROBLEMS error state (stale 3.0.4 linux-x64 binaries) is now resolved with properly published 3.1.2 binaries. linux-arm64-musl removed as it was never an official optional dep.
package-lock.json	Version bumped from 3.1.1 to 3.1.2 with all six platform-specific optional dependencies updated to 3.1.2; libc fields (glibc/musl) properly added to Linux packages; integrity hashes all have correct SHA-512 base64 length.

Sequence Diagram

sequenceDiagram
    participant WF as publish.yml workflow
    participant GH as GitHub (PR #399)
    participant NPM as npm registry
    participant PR as This PR (#404)

    WF->>GH: Bump package.json → 3.1.2, update CHANGELOG
    GH-->>WF: PR #399 merged
    WF->>WF: Build native binaries (Rust crate @ 3.1.0 → compiled as 3.1.2)
    WF->>NPM: Publish @optave/codegraph-*@3.1.2 (all platforms)
    NPM-->>WF: Publish confirmed
    WF->>PR: Update Cargo.toml 3.1.0 → 3.1.2
    WF->>PR: Regenerate DEPENDENCIES.json (errors cleared)
    WF->>PR: Update package-lock.json 3.1.1 → 3.1.2 with new integrity hashes
    PR-->>GH: Automated PR #404 opened

Loading

_{Last reviewed commit: 1d57171}

[greptile-apps]

Cargo.toml skips version 3.1.1

The crates/codegraph-core/Cargo.toml jumps from 3.1.0 directly to 3.1.2, bypassing 3.1.1. Checking the git log confirms that the prior release commit (PR #399, 21ba896) bumped package.json to 3.1.2 but left Cargo.toml at 3.1.0 — meaning the npm package published at 3.1.1 had a mismatched Rust crate version.

If the crate is ever published independently to crates.io, or if tooling relies on version parity between the JS package and the native crate, this gap could cause confusion. It's worth verifying the publish workflow always keeps both versions in sync from now on, or explicitly documenting that Rust crate versions may lag behind npm patch releases.