[FEAT] Update Script?

[mynameistito]

Add a way to update via the cn commands, alongside potentially an update script?

[mylee04]

Thanks for opening this.

This is now shipped in v1.6.4. We added both cn update and cn update check, so existing installs can now report and use the right update path depending on how code-notify was installed.

If you already have code-notify installed, please try:

cn update
cn update check

Release: https://github.com/mylee04/code-notify/releases/tag/v1.6.4

If you get a chance, please update and let us know if it works as expected on your setup.

[mynameistito]

Thanks for opening this.

This is now shipped in v1.6.4. We added both cn update and cn update check, so existing installs can now report and use the right update path depending on how code-notify was installed.

If you already have code-notify installed, please try:

cn update
cn update check
Release: https://github.com/mylee04/code-notify/releases/tag/v1.6.4

If you get a chance, please update and let us know if it works as expected on your setup.

Hey Just did so thanks!

However it outputs like this?

It would be good to potentially add a check to see if it's actually needs an update?

PS C:\Users\mynameistito> cn update

[>] Updating Code-Notify

 ====================================
   Code-Notify for Windows v1.6.4
 ====================================


Checking prerequisites...
[OK] PowerShell version: 7.6.0
[OK] Windows version: 10.0
[OK] BurntToast module: Installed (enhanced notifications)
[OK] Git: Installed (project detection enabled)

Installing Code-Notify...
[OK] Created PowerShell module
[OK] Created notification script
[OK] Created CLI wrappers

Configuring PATH...
[i] Already in PATH: C:\Users\mynameistito\.code-notify\bin

Configuring PowerShell profile...
[i] Aliases already in PowerShell profile
[OK] Update complete!
[i] Run 'code-notify version' in a new shell to confirm the installed version
PS C:\Users\mynameistito> cn update check

[i] Checking for updates...
To update code-notify, run:
  irm https://raw.githubusercontent.com/mylee04/code-notify/main/scripts/install-windows.ps1 | iex
PS C:\Users\mynameistito>

[mylee04]

Thanks for testing this again and for calling that out.

That follow-up is now shipped in v1.6.5. We updated the behavior so that:

• cn update check now compares your installed version against the latest GitHub release
• cn update now skips the reinstall flow when you are already up to date
• Windows cn version now writes pipeline-friendly output, which also fixed the CI/update-check path around this

Release: https://github.com/mylee04/code-notify/releases/tag/v1.6.5

If you get a chance, please run cn update once more and let us know whether the new output looks right on your machine.

[mynameistito]

Here ya go @mylee04

PS C:\Users\mynameistito> cn update

[>] Updating Code-Notify

 ====================================
   Code-Notify for Windows v1.6.5
 ====================================


Checking prerequisites...
[OK] PowerShell version: 7.6.0
[OK] Windows version: 10.0
[OK] BurntToast module: Installed (enhanced notifications)
[OK] Git: Installed (project detection enabled)

Installing Code-Notify...
[OK] Created PowerShell module
[OK] Created notification script
[OK] Created CLI wrappers

Configuring PATH...
[i] Already in PATH: C:\Users\mynameistito\.code-notify\bin

Configuring PowerShell profile...
[i] Aliases already in PowerShell profile
[OK] Update complete!
[i] Run 'code-notify version' in a new shell to confirm the installed version
PS C:\Users\mynameistito> cn update

[i] Checking for updates...
[i] Current version: 1.6.5
[i] Latest release: 1.6.5
[OK] Already up to date
PS C:\Users\mynameistito>

Time to add cn update to my Update-All Function 😅 https://github.com/mynameistito/.dotfiles/blob/main/Documents/PowerShell/Microsoft.PowerShell_profile.ps1

[mynameistito]

Oh one more potential thing that might be needed?

I have a auto trust thing setup which lives in my ~/.claude

# Auto-trusts every directory in Claude Code's .claude.json
$claudeJson = "$env:USERPROFILE\.claude.json"

try {
    $data = Get-Content $claudeJson -Raw | ConvertFrom-Json
    $changed = $false
    foreach ($key in $data.projects.PSObject.Properties.Name) {
        if ($data.projects.$key.hasTrustDialogAccepted -eq $false) {
            $data.projects.$key.hasTrustDialogAccepted = $true
            $changed = $true
            Write-Host "Trusted: $key"
        }
    }
    if ($changed) {
        $data | ConvertTo-Json -Depth 20 | Set-Content $claudeJson -Encoding UTF8
        Write-Host "Done. Closing in 3 seconds..."
        Start-Sleep 3
    } else {
        Write-Host "All projects already trusted. Nothing to do." -ForegroundColor Green
        Start-Sleep 2
    }
} catch {
    Write-Host "Error: $_"
    Start-Sleep 5
}

Unsure if it's needed but could be a nice to have.

[mylee04]

That seems like the safer direction to me.

Rather than auto-modifying Claude trust state, a better first step is probably this:

• when cnp on runs, detect whether the current project is not trusted yet
• show a warning instead of changing trust automatically

That keeps the security boundary explicit, and it also makes it much clearer why project hooks might not behave the way the user expects.

I am going to try implementing that approach next.

[mynameistito]

Yeah that would be good then have a prompt to enable @mylee04 or w/e

Happy to also yap on discord too if easier and you want feedback or whatever!

mynameistito is the handle ☺️