Verify live artifact state
store-statusworkflowsetup L3★1,223
sceneview/sceneview ↗What it does
Verify live publish state of SceneView artifacts
Best for
Verifying real live artifact availability after CI passes; CI-green is never proof of live for app stores, CDN, and package registries.
Inputs
- · [object Object]
Outputs
- · [object Object]
- · [object Object]
Requires
- · curl (iTunes lookup, Maven HTTP HEAD, npm CLI)
- · gradle.properties (for expected version if not passed)
Preconditions
- · Ollama/Granola/network available for curl calls
- · Expected version resolved from args.version or gradle.properties
- · Each probe (iOS, Maven, npm) runs in parallel
- · Failed probe (null) is tolerant; others continue
Failure modes
- · CI-green but artifact not published to iTunes/Maven/npm → probes detect (versioning lag)
- · Version number unparseable → validation regex catches
- · Network transient failure → graceful null, no false mismatch
- · ASC reject state or Play review pending → documented gap (needs browser auth)
- · Package name typo (sceneview-web vs sceneview) → probe detects mismatch
Trust signals
- · Direct iTunes API call (not web scrape)
- · Maven HTTP 200 is ground truth (not just build success)
- · npm exact version match (not dist-tag)
- · STATE.md store/live bullet auto-updated (audit trail)
- · Version resolved from source, not guessed