Bump Electron to v41.5.0+wvcus [CURRENT MAJOR]

[github-actions]

Electron Version Update (Current Major Version)

This PR updates Electron to the latest current major version: v41.5.0+wvcus

Changes

• Updated package.json electron dependency
• Updated bun.lock with new electron version and commit hash

Auto-generated

This PR was automatically generated by the Electron Version Updater workflow.

[greptile-apps]

Greptile Summary

This auto-generated PR bumps the Electron dependency from v41.1.1+wvcus to v41.5.0+wvcus, staying within the same major version (v41) using the castlabs electron-releases GitHub source.

• package.json: version tag updated to point at the new castlabs release tag.
• bun.lock: commit hash updated from 57d9d04 to 0527cd6, but the SHA512 integrity hash is unchanged between the two versions — worth verifying this is expected behavior for Bun's handling of GitHub-sourced packages.

Confidence Score: 4/5

The change is a minor patch bump within the same major Electron version; the only concern is the unchanged SHA512 integrity hash in the lockfile for what should be different package content.

Both changed files are straightforward version references. The integrity hash in bun.lock being identical for two different commits of a significant dependency (Electron 41.1.1 → 41.5.0) is unexpected and reduces confidence that the lockfile was fully regenerated correctly or that integrity checking will catch content changes for this package.

bun.lock — the SHA512 integrity hash for the electron entry should be verified to have changed as expected for the new commit.

Important Files Changed

Filename	Overview
package.json	Electron dependency version updated from v41.1.1+wvcus to v41.5.0+wvcus (same major, patch bump via castlabs GitHub releases).
bun.lock	Lockfile updated with new commit hash (57d9d04 → 0527cd6) and version tag, but the SHA512 integrity hash is identical to the previous version, which is unexpected for a non-trivial version jump.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[package.json\nelectron: github castlabs/electron-releases] --> B{Version Change}
    B --> C[Old: v41.1.1+wvcus\ncommit 57d9d04]
    B --> D[New: v41.5.0+wvcus\ncommit 0527cd6]
    D --> E[bun.lock entry updated\ncommit hash: 0527cd6]
    E --> F{SHA512 integrity}
    F --> G[⚠️ Unchanged hash\nsha512-yK7cGZr3Wdz...]
    C --> H[Old SHA512\nsha512-yK7cGZr3Wdz...]
    G -.->|Same value| H

Loading

_{Reviews (1): Last reviewed commit: "chore: bump electron to v41.5.0+wvcus [C..." | Re-trigger Greptile}

[greptile-apps]

Identical integrity hash across version bump

The sha512 integrity hash for the electron package is unchanged between the old entry (commit 57d9d04, v41.1.1+wvcus) and the new entry (commit 0527cd6, v41.5.0+wvcus). A version jump from 41.1.1 to 41.5.0 should produce a different tarball, and thus a different SHA512. If Bun validates this hash against the downloaded archive, the unchanged hash means the integrity check offers no protection against version confusion or unexpected content for the new commit.