nhcarrigan/hikari-desktop
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 9 Pull Requests 36 Actions Releases 22 Activity

chore: update SUPPORTED_CLI_VERSION to 2.1.104 (v2.1.104) #260

New Issue
Closed
opened 2026-04-13 09:12:17 -07:00 by hikari · 1 comment
hikari commented 2026-04-13 09:12:17 -07:00
Owner
Copy Link
Copy Source

Context

The changelog audit from v2.1.80 to v2.1.104 is now complete. Issues have been filed for all relevant changes that require implementation work:

  • #253 — CwdChanged and FileChanged hook events (v2.1.83)
  • #254 — TaskCreated hook event (v2.1.84)
  • #255 — Idle-return prompt after 75+ minutes (v2.1.84)
  • #256 — PermissionDenied hook event (v2.1.89)
  • #257 — defer permission response for PreToolUse hooks (v2.1.89)
  • #258 — Monitor tool in stream parsing (v2.1.98)
  • #259 — disableSkillShellExecution config exposure (v2.1.91)

Changes reviewed and consciously skipped (not relevant to the desktop wrapper):

  • --bare flag — scripted/CI use case, not applicable to our interactive session model
  • Bedrock / Vertex AI setup wizards — pure CLI UI, no stream-json impact
  • /tag and /vim command removal — not present in our slash command list
  • Default effort level change (medium → high) — no effort level UI in Hikari Desktop
  • refreshInterval status line setting — we don't parse/display status line config
  • CLAUDE_CODE_PERFORCE_MODE env var — too niche for general exposure
  • /team-onboarding command — CLI-side feature, no stream-json representation
  • --channels permission relay — relay infrastructure, not our concern
  • managed-settings.d/ drop-in directory — admin/enterprise feature
  • Various provider/auth fixes — not relevant to our wrapper layer
  • X-Claude-Code-Session-Id header — HTTP transport detail, not stream-json
  • CLAUDE_CODE_NO_FLICKER=1 / focus view toggle — TUI rendering, irrelevant in stream-json mode

Tasks

  • Update SUPPORTED_CLI_VERSION in src/lib/components/CliVersion.svelte from "2.1.80" to "2.1.104"
  • Update the audit record in the project memory file

References

  • src/lib/components/CliVersion.svelte line 5

✨ This issue was created with help from Hikari~ 🌸

## Context The changelog audit from **v2.1.80** to **v2.1.104** is now complete. Issues have been filed for all relevant changes that require implementation work: - #253 — `CwdChanged` and `FileChanged` hook events (v2.1.83) - #254 — `TaskCreated` hook event (v2.1.84) - #255 — Idle-return prompt after 75+ minutes (v2.1.84) - #256 — `PermissionDenied` hook event (v2.1.89) - #257 — `defer` permission response for PreToolUse hooks (v2.1.89) - #258 — Monitor tool in stream parsing (v2.1.98) - #259 — `disableSkillShellExecution` config exposure (v2.1.91) Changes reviewed and **consciously skipped** (not relevant to the desktop wrapper): - `--bare` flag — scripted/CI use case, not applicable to our interactive session model - Bedrock / Vertex AI setup wizards — pure CLI UI, no stream-json impact - `/tag` and `/vim` command removal — not present in our slash command list - Default effort level change (medium → high) — no effort level UI in Hikari Desktop - `refreshInterval` status line setting — we don't parse/display status line config - `CLAUDE_CODE_PERFORCE_MODE` env var — too niche for general exposure - `/team-onboarding` command — CLI-side feature, no stream-json representation - `--channels` permission relay — relay infrastructure, not our concern - `managed-settings.d/` drop-in directory — admin/enterprise feature - Various provider/auth fixes — not relevant to our wrapper layer - `X-Claude-Code-Session-Id` header — HTTP transport detail, not stream-json - `CLAUDE_CODE_NO_FLICKER=1` / focus view toggle — TUI rendering, irrelevant in stream-json mode ## Tasks - [ ] Update `SUPPORTED_CLI_VERSION` in `src/lib/components/CliVersion.svelte` from `"2.1.80"` to `"2.1.104"` - [ ] Update the audit record in the project memory file ## References - `src/lib/components/CliVersion.svelte` line 5 ✨ This issue was created with help from Hikari~ 🌸
hikari commented 2026-04-13 13:51:07 -07:00
Author
Owner
Copy Link
Copy Source

Resolved in PR #261. Updated SUPPORTED_CLI_VERSION constant in CliVersion.svelte from "2.1.80" to "2.1.104". ✨

Resolved in PR #261. Updated `SUPPORTED_CLI_VERSION` constant in `CliVersion.svelte` from `"2.1.80"` to `"2.1.104"`. ✨
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gurkirat hanna (Hanna Rose) hikari (Hikari) minori (Minori) naomi (Naomi Carrigan) rain teklu tim
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/hikari-desktop#260
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?