NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
iOS implementation of attested_secure_keys: hardware-backed, attestable EC P-256 keys via the Secure Enclave and App Attest.
Last release 2 months ago
10 Aug 2026
Too new to tell
only 2 release windows
Nearly every release is documented
notes for 2 of 2 stable releases
Nothing withdrawn
no release was ever pulled
3 months old
4 releases · first in 2026
One column per month.
The v0.1.1 tag failed to publish anything. Only the app-facing package was bumped, which broke both workflows: CI's version-lockstep gate rejected the
The v0.1.1 tag failed to publish anything. Only the app-facing package was
bumped, which broke both workflows: CI's version-lockstep gate rejected the
0.1.0/0.1.1 mix, and the publish job aborted on its first step because
attested_secure_keys_platform_interface was still 0.1.0, a version pub.dev
already has.
Bump the platform interface and the two implementation packages to 0.1.1 so
the set is back in lockstep. No code or API changes in any of them.
Also guard each publish step with .github/scripts/publish-if-new.sh, which
skips a package whose version is already on pub.dev. dart pub publish
treats that case as a hard error, so a re-run after a partial release would
otherwise keep dying on the packages that already uploaded.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
attested_secure_keys 0.1.1.release: 0.1.0 (first stable) + clarify verification responsibility
release: 0.1.0 (first stable) + clarify verification responsibility
First stable release. Secure Enclave + App Attest device-verified on a physical
iPhone. No functional changes since 0.1.0-dev.2.
Renamed the iOS keychain service identifiers from ro.roeid.* to io.github.exilonx.*. No API change. Note: keys stored by 0.1.0-dev.1 used the old iden
ro.roeid.* to
io.github.exilonx.*. No API change. Note: keys stored by 0.1.0-dev.1 used
the old identifiers and won't be found after upgrading — acceptable for a
prerelease with no production installs; regenerate keys.First prerelease; Secure Enclave + App Attest device-verified on a physical iPhone. Secure Enclave implementation of AttestedSecureKeysApi: EC P-256 k
First prerelease; Secure Enclave + App Attest device-verified on a physical
iPhone. Secure Enclave implementation of AttestedSecureKeysApi:
EC P-256 keygen + ES256 signing via CryptoKit, keychain blob persistence,
capability reporting, biometric gating via SecAccessControl, and an App Attest
scaffold that binds the key's JWK thumbprint + server nonce.
Your coding agent can read these notes before it upgrades. Set up the MCP server →