Skip to content

spaceapp setup 1.0.31

Choose a tag to compare

View all tags
@oll4com oll4com released this 01 Oct 03:32
· 96 commits to main since this release
v1.0.31
898ad37

SpaceApp setup 1.0.31

Known issue: upgrades using run-spaceapp update fail in this version because the temporary staging directory is missing its base compose.yml. Existing installations should wait for a corrected version before upgrading. Fresh installations passed validation on Linux, Windows 11 and macOS Intel.

Install

For a new installation:

npx --yes run-spaceapp@1.0.31 install

The npm latest and next tags currently point to 1.0.31.

Published artifacts

  • npm: run-spaceapp 1.0.31
  • Container images: ghcr.io/oll4com/spaceapp-core:1.0.31, ghcr.io/oll4com/spaceapp-cli:1.0.31, ghcr.io/oll4com/spaceapp-browser:1.0.31
  • All three images include linux/amd64 and linux/arm64 manifests, SBOMs and provenance.
  • Published source commit: 2769d82e1077c9316c6452f40c4996e0290ce083.
  • npm tarball SHA256: 3930c254305195988e14fc7456383638d795c2440c9f053062b97a10d153e060; matches the accepted CI artifact.

Changes and validation

Dependency JavaScript/CSS source maps are removed after compilation to keep the ARM64 core image within the existing 900 MiB limit. Runtime code and licenses are preserved. Core ARM64 is 879.0 MiB; CLI ARM64 is 1049.2 MiB; browser ARM64 is 1544.3 MiB.

Source checks and all six architecture/container checks passed, including the existing size and fixable MEDIUM/HIGH/CRITICAL vulnerability gates. Published npm package integrity, source commit and provenance were checked. Public npm fresh installations passed on Linux, Windows 11 and macOS Intel. ARM64 image validation does not constitute Apple Silicon or Windows ARM host testing.

Post-publication registry upgrades from retained older installations failed on all three tested operating systems because of the staging Compose issue above. Earlier local-image tests did not exercise the real image-pull path. The failures occurred before checkpoint/cutover; the original lab installations were restored and verified with preserved secrets and workspaces. Upgrade acceptance remains incomplete.

Workflow status

Release workflow 36748438249 successfully published the images and npm package. Its final npm metadata check timed out during registry propagation, leaving the workflow marked failed. The registry metadata and published tarball were subsequently verified independently. This release does not change that workflow result.

Assets 2
Loading