Skip to content

Bump electron-store from 11.0.2 to 12.0.0 - #251

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/electron-store-12.0.0
Open

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/electron-store-12.0.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 28, 2026 •

Copy link
Copy Markdown

Bumps electron-store from 11.0.2 to 12.0.0.

Release notes

Sourced from electron-store's releases.

v12.0.0

Breaking

  • Require Electron 35 1aa2096, f78f186
  • Update to conf 16 f78f186
    • Migrations no longer run for a config file that does not exist yet. A new store starts at the current version.
    • Migrations run in version order, whatever order they are defined in.
    • The recorded migration version never moves backwards.
    • .get() throws when given a non-string key.
    • The rootSchema option throws when it contains a properties key.
    • With clearInvalidConfig, the cleared store is now written to the config file.
    • projectVersion must be a full semantic version when using migrations.
    • name must not point outside cwd.
    • An empty encryptionKey is refused.
    • With dot notation, a key that is not a valid path (for example, a[x) throws.

New

  • Add cache option to keep the store in memory
    • Reads do not parse the config file each time. Values returned from the store are frozen, so copy a value before you change it.
  • Add .events to listen for change events directly
  • Allow serialize to return a Uint8Array
  • Allow the projectVersion option in the types 9fbe0a1
  • Make the name option non-readonly in the types 9d62519
  • Improve the TypeScript types. Annotating schema with Schema<T> now gives .get() its types.

Improvements

  • Fail with a clear error when not running in Electron, unless you pass an absolute cwd 44bd512
  • Update dependencies 1aa2096
  • Improve the docs, including the encryption algorithm, rootSchema, ajvOptions, configFileMode, nested defaults, and renderer process requirements 49ab1c3, e7cada4, 36f7106, 17122f8, 5ad6974

Fixes

  • Fix .reset() with dot-notation keys
  • Fix a migration with a semver range making the store impossible to open after a failed migration

Migration guide

Migrations

A new config file no longer runs migrations, so the store starts at the current version. If your migrations must run on first launch, do that work in your app code instead.

If you use migrations, the projectVersion (or your app version) must be a full semantic version, such as 1.0.0.


sindresorhus/electron-store@v11.0.2...v12.0.0

Commits
  • d5f575a 12.0.0
  • f78f186 Update to conf 16 and require Electron 35
  • 0d41a26 Tweaks
  • 5ad6974 Improve docs
  • e7cada4 Document the rootSchema, ajvOptions and configFileMode options
  • 17122f8 Spell out the renderer process requirement
  • 36f7106 Document defaults for nested schema properties
  • 44bd512 Fail with a clear error when not running in Electron
  • 9fbe0a1 Allow the projectVersion option in the types
  • 9d62519 Make the name option non-readonly
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies javascript Dependa-bot update for Javascript labels Oct 28, 2026
Bumps [electron-store](https://github.com/sindresorhus/electron-store) from 11.0.2 to 12.0.0.
- [Release notes](https://github.com/sindresorhus/electron-store/releases)
- [Commits](sindresorhus/electron-store@v11.0.2...v12.0.0)

---
updated-dependencies:
- dependency-name: electron-store
  dependency-version: 12.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/electron-store-12.0.0 branch from 8ba0b09 to 556b287 Compare October 31, 2026 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies javascript Dependa-bot update for Javascript

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants