Skip to content

chore(release): prepare 1.0.0 for SPM + Swift Package Index - #13

Merged
Dicky019 merged 2 commits into
mainfrom
chore/publish-1.0.0
Jun 27, 2026
Merged

Dicky019 merged 2 commits into
mainfrom
chore/publish-1.0.0

Conversation

@Dicky019

Copy link
Copy Markdown
Owner

Summary

Prepares ScreenUtil for its 1.0.0 release on Swift Package Manager and Swift Package Index. Release hygiene plus the publishing config and runbook — no public API changes.

Changes

Release hygiene

  • Pin swift-atomics to exact: "1.3.0" (lockstep, reproducible resolution).
  • Trim PrivacyInfo.xcprivacy to an empty NSPrivacyAccessedAPITypes — the four required-reason APIs it previously declared (UserDefaults, SystemBootTime, DiskSpace, FileTimestamp) are never used by the code, so the manifest now matches the "no data collection / no tracking" claim.
  • Remove the unused app-style Info.plist and its dangling exclude: in Package.swift.
  • Cut the 1.0.0 section in CHANGELOG.md.

Publishing

  • Add .spi.yml so Swift Package Index builds documentation for the ScreenUtil target.
  • Add PUBLISHING.md — a runbook for accounts, repo settings, tag/GitHub Release, and SPI submission.

Verification

  • swift build — clean, no warnings.
  • swift test — 108 tests, 0 failures.

Notes

  • Scope is SPM + Swift Package Index only for now. CocoaPods/Carthage are out of scope.

Dicky019 added 2 commits June 28, 2026 01:48
Pin swift-atomics to exact 1.3.0, trim the privacy manifest to the APIs actually used (none required-reason), drop the unused app Info.plist, and cut the 1.0.0 changelog section.
PUBLISHING.md walks accounts, repo settings, tag/release, and SPI submission. .spi.yml builds docs for the ScreenUtil target on Swift Package Index.
@Dicky019
Dicky019 merged commit 9f2245b into main Jun 27, 2026
4 checks passed
@Dicky019
Dicky019 deleted the chore/publish-1.0.0 branch June 27, 2026 16:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant