Skip to content

v1.2.2 Bug-fix

Latest

Choose a tag to compare

@Multivalence Multivalence released this 01 Aug 21:38

[1.2.2] — 2026-08-01

Bug-fix release. Credential-bearing cookies were not carried through profile
duplication, export, or import. No new permissions, no schema change, and no
change to how credentials are stored.

Fixed

Duplicating a profile silently shared its cookie credential

  • Duplicating a profile whose only credential was a cookie skipped the
    "configuration only / reuse / new credential" prompt entirely and fell
    through to the default
  • Because the duplication step also ignored cookies, the copy kept a reference
    to the original's stored secret. The result was a shared credential the user
    was never asked about, where editing one profile's cookie would change the
    other's
  • The prompt now appears whenever a profile holds any credential, cookie or
    header, and all three duplication modes apply to cookies:
    • Configuration only clears the cookie's secret reference and marks it as
      needing a credential
    • Reuse the existing credential keeps the same reference, as intended
    • New independent credential creates a fresh secret and asks for its value
      Exports omitted cookie credentials
  • "Export with credentials" produced an empty value for every cookie, so a
    backup looked complete but restored a profile with no working cookie
  • A configuration-only export wrote an empty string rather than the null
    placeholder an import reads, so restored profiles were not correctly marked
    as needing a credential
  • Both export modes now handle cookies exactly as they handle headers
    Imports ignored cookie credentials
  • Credential cookies in an imported file were not detected, so their values
    were neither reported to the user nor moved into the active storage mode
  • Imported cookie credentials are now detected, disclosed before import, and
    stored under whichever credential mode is currently selected
  • Import entries are keyed by section as well as name, so a header and a cookie
    sharing a name can no longer overwrite one another

Notes

Ordinary cookies such as locale were unaffected throughout and continue to
copy, export, and import with their values intact.

If you duplicated a profile containing a credential cookie on 1.2.1, check
whether the copy is sharing the original's credential: open the cookie row and
look for the "Shared" marker. Re-duplicating on this version gives the choice
that should have been offered.