Skip to content

Update check: frequency setting ineffective, notice suggests the wrong command #19

Open

Description

@barisgit

Found during #17 review.

  • main._check_for_updates_if_needed (~61-65) records the check timestamp only when an update is found, so update_check_frequency has little effect (the 24-hour PyPI cache from refactor: enforce maximum strictness across the codebase #17 limits the damage).
  • The notice suggests kilm update, which only prints help; it should say kilm update perform.
  • An unknown latest version is reported as up to date.
  • The auto_update setting and the force_check parameter are never used: implement or remove.
  • The root --help runs the update check; help output should not depend on the network.

Activity

  1. added a commit that references this issue on Oct 26, 2026
    97a28f4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions