v0.6.0

[0.6.0] - 2026-10-27

Changed

• auth reuse now takes its decision from agent-cli-kit's shared reuse
  package, the family's rule for reusing a login. Contexts on the server whose
  email the stored password verifies still come first, and a context without an
  email is still never read. When the keychain itself shows that every one of
  them is rejected, the password stored for the server under the context's own
  key is tried with each email recorded for the server, so a password no
  context with an email points at any more is still found. These further
  checks run within ten seconds of the start (or --timeout when shorter),
  adopt only on that keychain evidence, and otherwise leave the earlier answer.
  A scheme supplied by --auth-scheme, WECOM_CALENDAR_AUTH_SCHEME, .env or
  a password variable keeps reuse to the contexts. A password missing for one
  context no longer fails the command when another context's login verified
  and the keychain answered during the run, and a rejected password is tried
  once per run. Two spellings of one email are still one identity.
• The auth reuse result adds scheme, username and next_steps (doctor
  after reused or unchanged, the same command without --dry-run after
  available, auth guide and auth login after unavailable);
  AUTH_REUSE_AMBIGUOUS adds details.candidates.
• config set-context, auth guide, AUTH_NO_BASIC,
  CREDENTIAL_NOT_VISIBLE_OR_MISSING and an unhealthy doctor now offer
  wecom-calendar-cli --use-context '<name>' auth reuse, which runs reuse
  directly, instead of auth reuse --dry-run. An HTTP 401 lists it first too
  when the config file shows a stored login could apply.
• Update the companion Skill to 0.5.1 for auth reuse.

Added

• auth reuse --from-scheme basic selects the password stored for the server,
  paired with each WeCom email recorded for it or, with --from-context, with
  that context's email.

Fixed

• config delete-context and a config init edit no longer delete a stored
  password that a context without a stored server URL still resolves through
  the public endpoint, for example a team preset completed by auth reuse.

What's Changed

• Prefer long-lived credentials when reusing a login by @AngelMsger in #10
• Prepare v0.6.0 by @AngelMsger in #11

Full Changelog: v0.5.1...v0.6.0

v0.5.1

What's Changed

• fix(auth): preserve credential outcomes with kit v0.4.0 by @AngelMsger in #6
• refactor(skill): use the kit's shared Skill rules by @AngelMsger in #7
• docs: split AGENTS.md into rules, design and history by @AngelMsger in #8
• Prepare v0.5.1 by @AngelMsger in #9

Full Changelog: v0.5.0...v0.5.1

v0.5.0

What's Changed

• Never raise the macOS keychain reset dialog by @AngelMsger in #1
• Use agent-cli-kit for the shared packages by @AngelMsger in #2
• Use agent-cli-kit's auth and config packages by @AngelMsger in #3
• Point the family links at agent-clis by @AngelMsger in #4
• Prepare v0.5.0 by @AngelMsger in #5

New Contributors

• @AngelMsger made their first contribution in #1

Full Changelog: v0.4.0...v0.5.0

v0.4.0

Full Changelog: v0.3.0...v0.4.0

v0.3.0

Full Changelog: v0.2.3...v0.3.0

v0.2.3

Full Changelog: v0.2.1...v0.2.3

v0.2.1

Full Changelog: v0.2.0...v0.2.1

v0.2.0

Full Changelog: v0.1.0...v0.2.0

v0.1.0

Full Changelog: https://github.com/AngelMsger/wecom-calendar-cli/commits/v0.1.0