Merge pull request #1 from MFB-Technologies-Inc/v14.8.0

V14.8.0

Author: r-jarvis

.github/workflows/ci.yml

@@ -0,0 +1,21 @@
+name: ci
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - "*"
+  workflow_dispatch:
+
+jobs:
+  build:
+    runs-on: macos-15
+    environment: default
+    steps:
+      - uses: actions/checkout@v4
+      - name: Select Xcode 16.3
+        run: sudo xcode-select -s /Applications/Xcode_16.3.app/Contents/Developer
+      - name: Resolve frameworks
+        run: swift package resolve

Package.swift

@@ -0,0 +1,30 @@
+// swift-tools-version: 6.1
+
+import PackageDescription
+
+let package = Package(
+    name: "PSPDFKit-SP-Mirror",
+    platforms: [
+        .iOS(.v16),
+        .macCatalyst(.v16),
+        .visionOS(.v1),
+    ],
+    products: [
+        .library(
+            name: "PSPDFKit",
+            targets: ["PSPDFKit", "PSPDFKitUI"]
+        )
+    ],
+    targets: [
+        .binaryTarget(
+            name: "PSPDFKit",
+            url: "https://github.com/MFB-Technologies-Inc/PSPDFKit-SP-Mirror/releases/download/pre-14.8.0/Nutrient-iOS-SDK-PSPDFKit.xcframework-14.8.0.zip",
+            checksum: "15e36d61b47ee7aafa26ddfd83b734a7eb931d3a3986a0959dcc08c050ed56a3"
+        ),
+        .binaryTarget(
+            name: "PSPDFKitUI",
+            url: "https://github.com/MFB-Technologies-Inc/PSPDFKit-SP-Mirror/releases/download/pre-14.8.0/Nutrient-iOS-SDK-PSPDFKitUI.xcframework-14.8.0.zip",
+            checksum: "d9d97b5c9509f65803f9d39c32c7c9a1217584068eaf31176daea7114ad02662"
+        ),
+    ]
+)

README.md

@@ -1,3 +1,9 @@
 # PSPDFKit-SP-Mirror
 
 This is a version of https://github.com/PSPDFKit/PSPDFKit-SP backed by CDN instead of downloading straight from S3.
+
+## Updating for new releases
+
+Create a new branch named `feature/{{ new version }}`. Update the URLs and hashes for each framework. Create a release on this branch where the tag is `pre-{{ new version }}` with the framework zip files attached. The `pre-` part of the tag name is important because it prevents SPM from resolving that tag as the next version. This release should NOT be marked as latest.
+
+Once the PR is merged, create a new release where the tag is the appropriate version number and should be marked as latest.