Skip to content

scry v0.4.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 05 Aug 09:48
v0.4.0
fc9affb

Highlights

Edit custom fields from the TUI. Press e on any issue: pick one of your editable fields, then pick a value from what Jira actually allows on that issue — single select for options, multi-select (with current values preselected) for option/version arrays, your member list for user fields. No free-text input anywhere; a clear entry empties the field. The same allowlist and value shaping now drive both the web editor and the TUI (internal/fields).

Update notices on every surface. scry now checks GitHub releases at most once a day (anonymous GET to api.github.com, nothing sent, cached on disk) and tells you when a newer version exists — after scry sync, in scry status (and its --json), as a badge in the TUI header, and as a link in the web sidebar. Opt out with updateCheck: false; dev builds never check.

TUI shows your custom fields. The detail view renders discovered field specs with their labels, and body-role fields (team-specific description/analysis/result fields) as prose sections.

Hosted demo works — or says why not. In-app browsers (Twitter/X, Instagram) block the service worker the zero-install demo runs on; instead of an eternal loading skeleton you now get a clear notice with a copy-link button. The service-worker handshake is raced against a deadline, so restricted WebViews that hang (rather than fail) also land on the notice.

Notes

  • The update check is the only network call scry makes besides your Jira site, and it carries no identity. See SECURITY.md.
  • Upgrade: brew upgrade midagedev/tap/scry, or grab a binary below.
Assets 9
Loading