mirror of https://github.com/sudosylabs/vnidrop.git synced 2026-08-05 02:29:55 +02:00

Files

cdricms ff391f5502 build(apple): publish prebuilt core bundle in release assets

Bundle the compiled Apple core — vnidrop.xcframework plus the generated UniFFI
bindings (Vnidrop.swift, a source file that lives outside the xcframework) — into
VnidropCore-<version>.zip with a checksum, and attach it to the GitHub Release.
This lets a consumer (e.g. Xcode Cloud, later) use the prebuilt core instead of
installing Rust and running build-core.sh.

No duplicate builds: the release job compiles the core once (build-apple-dmg ->
build-core.sh release), links it into the signed DMG, and package-core.sh only
zips that same output. Package.swift is unchanged (still binaryTarget(path:)).

- apple/scripts/package-core.sh: stage xcframework + Vnidrop.swift and zip them
  with a sha256sum/shasum-compatible checksum sidecar (macOS-native).
- Makefile: package-apple-core target.
- apple-release.yml: run package-apple-core after the DMG and upload the zip +
  checksum in the macOS artifact.
- assemble-release.sh: verify the core zip's checksum, copy it into the final
  assets, and list it in release-manifest.json + SHA256SUMS (+ fixture update).

2026-07-31 11:40:34 +02:00

assemble-release.sh

build(apple): publish prebuilt core bundle in release assets

2026-07-31 11:40:34 +02:00

README.md

ci: automate Microsoft Store updates

2026-07-30 19:12:50 +02:00

test-assemble-release.sh

build(apple): publish prebuilt core bundle in release assets

2026-07-31 11:40:34 +02:00

test-release-config.sh

fix(release): configure Store CLI before settings

2026-07-31 04:51:31 +02:00

README.md

Coordinated releases

Only .github/workflows/release.yml responds to version tags. It verifies that the tag matches version.properties and points at the current master, then calls the native platform workflows in parallel.

The tag workflow runs only when the repository variable RELEASE_PIPELINE_ENABLED is exactly true. Leave it unset or set it to false to disable all coordinated releases, including Play uploads, without disabling release validation on pull requests.

Platform workflows upload private workflow artifacts. After every native build passes, the release pipeline:

stages the signed AAB as a draft on the configured Play closed-test track;
submits the unsigned .msixupload package to Microsoft Store certification;
downloads the universal APK signed by Play;
verifies and assembles the public artifacts;
generates checksums and GitHub build-provenance attestations;
creates exactly one GitHub Release;
updates the Homebrew cask.

Public GitHub Release assets are the DEB, RPM, notarized DMG, Sparkle appcast, Play-signed universal APK, checksum file, and release manifest.

The unsigned Microsoft .msixupload and upload-signed Android AAB remain private workflow artifacts. The protected microsoft-store GitHub Environment supplies the Partner Center credentials and Store product ID used to submit the Windows package. Microsoft publishes the update after certification; the job does not change Store listings, pricing, or availability. The Play release remains a draft on a closed-testing track; this pipeline cannot publish it to production.

To release, prepare and merge the new product version. Android, Microsoft Store, and Apple build/package versions are derived automatically:

make prepare-release RELEASE_VERSION=0.2.1
make check-version

Then create and push the matching tag:

git tag -s v0.2.1 -m "VniDrop 0.2.1"
git push origin v0.2.1

The tag must point at the current origin/master commit. A failed run creates no GitHub Release; a rerun safely reuses an already-staged Play draft only when the version, configured track, draft status, and app-signing certificate all match.