Skip to content

Update watchOS minimum version to 5 #363

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
dfed merged 2 commits into from
Jul 12, 2026
+2 −10
Merged

Update watchOS minimum version to 5 #363

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8a7d4e4
Update SwiftPM watchOS platform to v5
zunda-pixel Jul 12, 2026
55b3df4
Remove Requirements section from README
dfed Jul 12, 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
2 changes: 1 addition & 1 deletion Package.swift
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ let package = Package(
platforms: [
.iOS(.v12),
.tvOS(.v12),
.watchOS(.v4),
.watchOS(.v5),
.macOS(.v10_13),
],
products: [
Expand Down
8 changes: 0 additions & 8 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -207,14 +207,6 @@ Valet guarantees that reading and writing operations will succeed as long as wri
1. Running your app or unit tests without the application-identifier entitlement. Xcode 8 introduced a requirement that all schemes must be signed with the application-identifier entitlement to access the keychain. To satisfy this requirement when running unit tests, your unit tests must be run inside of a host application.
1. Attempting to write data larger than 4kb. The Keychain is built to securely store small secrets – writing large blobs is not supported by Apple's Security daemon.

## Requirements

* Xcode 16.0 or later.
* iOS 12 or later.
* tvOS 12 or later.
* watchOS 4 or later.
* macOS 10.13 or later.

## Migrating from prior Valet versions

The good news: most Valet configurations do _not_ have to migrate keychain data when upgrading from an older version of Valet. All Valet objects are backwards compatible with their counterparts from prior versions. Valets that have had their configurations deprecated by Apple will need to migrate stored data.
Expand Down
2 changes: 1 addition & 1 deletion Valet.podspec
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ Pod::Spec.new do |s|
s.frameworks = 'Security'
s.ios.deployment_target = '12.0'
s.tvos.deployment_target = '12.0'
s.watchos.deployment_target = '4.0'
s.watchos.deployment_target = '5.0'
s.macos.deployment_target = '10.13'

s.tvos.exclude_files = 'Sources/Valet/SinglePromptSecureEnclaveValet.swift'
Expand Down
Loading