Skip to content

Release 33.6

Choose a tag to compare

View all tags
@github-actions github-actions released this 18 Sep 02:29
· 5 commits to master since this release
33.6
e34ce25

What's new

  • Added cronitor auth login for browser-based sign-in or account creation. cronitor signup uses the same flow.
  • Added cronitor auth status to inspect the current machine credential without printing its key, and cronitor auth logout to revoke it and remove it locally.
  • Added --no-browser for remote terminals and agent-guided login, using the production WorkOS application by default.
  • Protected logout from conflicting API-key environment or flag overrides. Unconfirmed revocation preserves the local credential unless local-only removal is explicitly requested with --force.
  • Updated CLI and agent onboarding documentation for browser login and persistent credentials.
  • Corrected ping --metric help to show the name=value format.
  • Updated dashboard dependencies and removed the unused extract-zip dependency.

Sign in or create an account

cronitor auth login
cronitor auth status

For a remote terminal, use cronitor auth login --no-browser and keep the command running while you complete sign-in or signup at the displayed verification URL. Existing API-key configurations continue to work; CI and containers can keep using credentials from their secret manager.

Persistent credentials and scheduled jobs

Login saves a named, long-lived machine credential in the selected config file and restricts that file to its owner. Choose a writable config owned by the user that runs the CLI; use CRONITOR_CONFIG or --config for a custom path. Jobs running as another OS user need their own accessible config or credentials in their service environment.

cronitor auth logout revokes this installation's credential. Scheduled jobs using it will stop authenticating, so do not log out as routine cleanup after an agent task. Replacing a credential with another login does not revoke the previous one. Machine credentials are organization-owned and are not automatically revoked when a user's role changes or the user is removed; manage unused keys in the Cronitor dashboard.

Full-access users receive SDK Integration credentials. Read-only users receive telemetry-only credentials and cannot manage account resources through the CLI.

Assets 29
Loading