Skip to content

UseMyCurrentAccount++ v1.1.8

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 08 Aug 10:40
· 1 commit to main since this release
v1.1.8
d447ae1

Changelog

v1.1.8

  • Remove publisher-account, Cloud project, OAuth client, Partner Center product, and Store identifiers from tracked public documentation.
  • Keep project-specific publication identifiers exclusively in the ignored local publication runbook.

v1.1.7

  • Normalize accidental clipboard line breaks in protected Edge publisher credentials before building API headers.
  • Keep Edge API failures redacted and covered by automated publisher tests.

v1.1.6

  • Replace redundant byte-identical Chrome and Edge archives with one browser-neutral chromium-stores ZIP.
  • Attach the package once in GitHub Releases and submit the exact same verified bytes to both browser stores.
  • Remove same-version legacy package names and enforce the one-archive contract in CI and release tests.

v1.1.5

  • Require manual release retries to resolve an existing exact refs/tags/vX.Y.Z tag on main.
  • Prevent a same-named branch or mismatched version from reaching either Store publisher.

v1.1.4

  • Add automated Microsoft Edge Add-ons packaging, upload, operation polling, and certification submission.
  • Add Edge listing guidance, promotional assets, protected-environment configuration, and first-release duplicate guards.
  • Make GitHub Releases, Chrome publication, and Edge publication consume the same verified build artifact.

v1.1.3

  • Make account-picker auto-connect target only visible, actionable account controls and confirm that Microsoft continued sign-in.
  • Retry an unresponsive matching tile safely, deduplicate concurrent picker runs, and report bounded activation failures in diagnostics.
  • Rename the automation scope to All apps except exclusions.

v1.1.2

  • Preserve application-provided login_hint, domain_hint, and username values instead of injecting a conflicting hint.
  • Fail closed when top-level OAuth parameter names are percent-encoded and cannot be safely classified by Chromium rules.
  • Align the settings help, privacy notice, terms, Store listing, and loaded-extension QA with that precedence behavior.

Full Changelog: v1.1.1...v1.1.8

Assets 3
Loading