Repository navigation
Cloud-Visi v0.1.0-beta.2
Pre-releaseSource: 8a7a663eb3dbc57bfd2df45675fc8237b94797e6.
Added
- Local administrator sign-in, revocable sessions, repository-scoped viewer
grants, account administration, CSRF protection and authenticated snapshots. - Installation-bound trials, with signed offline keys valid for up to 30 days.
Expiry pauses access and sync while preserving data and renewal access. - Durable repository identity across providers, server scopes and reconnection;
independent commit membership for mirrored repositories. - Separate Terraform plan, apply and state observations, retained run attempts,
explicit cross-repository attribution and independent source/cloud filters. - Backend identity and configuration resolution with one selected workspace per
root and protection against unsafe target changes. - Dependencies through locals, variables and scoped modules; retained graph
generations, explicit historical reparse and scoped Azure/S3 cross-state paths.
Changed
- Integrates the Graphite & Butter interface colours with all approved features.
- Bounds scoped queries and evidence enrichment, and limits browser request
concurrency so authentication and trial checks remain responsive. - Missing evidence remains unconfirmed. A successful workflow or a resource in a
later state snapshot does not prove that a particular Terraform apply succeeded.
Upgrade requirements
- Back up the database and matching repository/encryption-key storage. Keep both
through the upgrade; do not remove volumes or replace the encryption key. - Configure
AUTH_PUBLIC_URLto the exact HTTPS origin behind your existing
trusted TLS proxy. New and upgraded installations require operator bootstrap
of the first administrator. See access setup. - Sign in before activating the installation-bound trial. Existing beta.1 installs
have no saved trial and need an owner-issued key for this release. - Application migrations are additive. Historical reparse/repair commands remain
explicit operator actions; no historical campaign is run by this release.
Verification and limits
-
AMD64 and ARM64 native readiness, sign-in, version and bundled scanner checks
passed against the published digest. Both architectures download anonymously.
The beta.1 image is unchanged; nolatesttag or OCI chart was published.
See image verification and the
release record. -
Fresh release verification: 2,012 Go test/subtest pass events across 28 packages,
46 explicit auth/upgrade/scoping harness pass events and 528 UI tests. UI lint,
TypeScript/Vite build, Go vet, 21 deployment checks and Helm lint passed.
Harness counts overlap the full suite; diagnostic/performance tests are opt-in. -
The verified synthetic partner profile is 20 repositories, 5,000 resources,
50,000 changes and five readers, including a passing uninterrupted two-hour soak. -
The 25,000-resource comparison still misses latency targets and is outside that
verified envelope. Synthetic results are not a customer workload guarantee. -
GitHub Actions coverage remains partial; DORA retains its Azure Pipeline limit.
-
Available state is an observation, not continuous cloud health or apply causality.
-
GCS, notifications, automatic remediation and OCI chart publication are excluded.
-
The locked UI build dependency
source-map-js1.2.1 has a
known source-map denial-of-service advisory.
It processes the trusted release source during build; the runtime image ships
the compiled static UI and Go server, without Node.js or that build package.
This release is not a claim of a vulnerability-free dependency inventory.
Pull the released image
docker pull ghcr.io/cloud-visi/cloud-visi:0.1.0-beta.2Approved multi-architecture digest: sha256:6b85bf671016716bbb56746e436bd8f0d82c06a56d4f26924dbe17f604d5bc40.
Archive SHA256: 1f6a0359ad7b8f681b102884d0dba80a23716fe479e5cb7872cf8e9a3f598339.
The beta alias matches this digest. latest remains absent. Native publication
and runtime verification: https://github.com/cloud-visi/cloud-visi-deploy/actions/runs/39019872885.
The attached record contains completed checks. Deployment and access setup
describes HTTPS, first-admin bootstrap, trial activation and data-preserving upgrades.