Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: uji/slack-wait
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.1.1
Choose a base ref
...
head repository: uji/slack-wait
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.1.2
Choose a head ref
  • 6 commits
  • 9 files changed
  • 2 contributors

Commits on Jun 3, 2026

  1. Refresh access token during long waits; keep it in memory only

    A long-running `wait` previously captured a single access token before the
    poll loop and never refreshed it, so once the token's lifetime elapsed every
    poll failed with invalid_auth until timeout. Introduce an in-memory Session
    that the Slack client queries before each request, refreshing transparently
    when the access token is missing or near expiry.
    
    Also stop persisting the access token: for rotating apps only the rotating
    refresh token is written to disk, and the access token lives in process memory,
    recreated from the refresh token on demand. Non-rotating apps (no refresh
    token) still persist their long-lived access token, which is their only
    credential.
    claude committed Jun 3, 2026
    Configuration menu
    Copy the full SHA
    92a8e30 View commit details
    Browse the repository at this point in the history
  2. Merge pull request #5 from uji/claude/slack-wait-token-refresh-BGXpB

    Refresh access token during long waits; keep it in memory only
    uji authored Jun 3, 2026
    Configuration menu
    Copy the full SHA
    0cd7762 View commit details
    Browse the repository at this point in the history
  3. Store refresh token in OS keyring

    Use github.com/99designs/keyring to persist refresh tokens in the
    system secure storage instead of a plain-text file:
    
    - macOS: Keychain
    - Linux: SecretService (GNOME Keyring / KDE Wallet 等)
    - Windows: Windows Credential Manager
    
    Tests use an injected in-memory keyring so they remain fast and portable.
    
    Note: existing users will need to re-authenticate with `slack-wait login`.
    claude committed Jun 3, 2026
    Configuration menu
    Copy the full SHA
    ae4c602 View commit details
    Browse the repository at this point in the history
  4. Merge pull request #6 from uji/claude/gifted-fermi-SDgWM

    Store refresh token in OS keyring
    uji authored Jun 3, 2026
    Configuration menu
    Copy the full SHA
    c43e675 View commit details
    Browse the repository at this point in the history
  5. Update docs and login message for OS keyring storage

    Replace references to token.json / "stored on disk" with OS keyring
    (macOS Keychain, Linux SecretService, Windows Credential Manager).
    claude committed Jun 3, 2026
    Configuration menu
    Copy the full SHA
    9d41c68 View commit details
    Browse the repository at this point in the history
  6. Merge pull request #7 from uji/claude/update-readme-keyring

    Update docs and login message for OS keyring storage
    uji authored Jun 3, 2026
    Configuration menu
    Copy the full SHA
    c08072c View commit details
    Browse the repository at this point in the history
Loading
⌂ 换网址