Skip to content

docs: add changelog entries for macOS codesigning and the crate refactor #789

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lwshang merged 2 commits into from
Sep 24, 2026
Merged

docs: add changelog entries for macOS codesigning and the crate refactor #789

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
18a00c7
docs: add changelog entries for macOS codesigning and the crate refactor
lwshang Sep 24, 2026
2bdd654
docs: drop the tap from the codesign entry and note notarization
lwshang Sep 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,9 @@ air-gapped signing

# Unreleased

* chore: the macOS `icp` release binaries are now code-signed with DFINITY's Developer ID certificate. This improves the Keychain experience for identities stored in the keyring. macOS used to treat each unsigned release as a different app, so choosing "Always Allow" lasted only until the next upgrade. The signed binary keeps the same identity across releases, so after you allow access once more on the first signed version, it stays allowed through later upgrades. The signed binary is what you get from the GitHub release (including the shell installer), the `dfinity/tap` Homebrew tap, and npm. `brew install icp-cli` from homebrew-core is not signed, because Homebrew builds that formula from source on its own infrastructure.
* chore: the codebase is reorganized as groundwork for running project operations inside a canister. The former `icp` library crate is split into `icp-project` (the project model and the build, install, sync and deploy operations) and `icp-app` (identities, settings, local networks and other machine-level state), and `icp-project` now reaches the file system, the network and sync plugins only through traits. This is internal only — no command, flag or manifest behavior changes.

# v1.5.0

* feat(sync-plugin): Introduced v0.2.0 of the sync-plugin interface. v0.1.0 plugins are still supported. v0.2.0 introduces the following features:
Expand Down
Loading