Skip to content

Latest commit

 

History

History
84 lines (49 loc) · 14.1 KB

prototype-delivery.md

File metadata and controls

84 lines (49 loc) · 14.1 KB

Alpha delivery

The development alpha uses prebuilt latest images. Each successful main-branch publication creates a tagged GitHub prerelease with Compose, the public environment template and a manifest containing exact image digests. Stable releases will use pinned versions.

Current release: alpha-43604526965-1, built from QOpenBB fbd81eaf11d82b47043592f60736009304f198c8, Workspace bf180ef506286886da224df9ff184cd1ace2397e and data API a965f70c164fe477ce9c99654b9be48e2f1bc9fd. Company Research is accepted within its bounded 13-task scope. Publication evidence binds CI jobs, assets and anonymous pulls; local runtime evidence remains tied to its original root4736c31/browserc9a267 and local images. A later documentation commit does not become the release build source. No CI-image browser or current owner-server acceptance is claimed.

Previous statement-period release: alpha-42878062405-1, built from QOpenBB e09024aa965757d23937ed0472ccce05d9666aea, Workspace e1a12c3a031a23598f41166a0f91b8fb24ac2387 and data API a965f70c164fe477ce9c99654b9be48e2f1bc9fd. Statement-period provenance is accepted, 7/7 tasks. Publication and packaged evidence distinguish local browser acceptance, public image identities and offline packaged checks. Its historical immutable pair and install-asset identities remain in its statement-period publication record. Owner-server deployment remains unverified.

Previous periodic-query release: alpha-42231784072-1, built from QOpenBB b37ec1963e1bc138115b431e3c168e5e48a8bd47, Workspace f832a5593223b1e702970c4de8eceda87a17fa5b and data API 2e60c0a7aff039eda5f14a9d494beaec822fb9c4. The repair preserves the periodic-only selector in Metrics/Ratios metadata. Evidence and acceptance scope distinguish source tests, four FMP queries, publication and packaged checks. The historical immutable pair remains in its publication record. This release has no owner-server deployment claim.

Previous company-selector release: alpha-42188370167-1, built from QOpenBB 1ee3576242ed8357dbd494c8b0f181eb92ac2809, Workspace f832a5593223b1e702970c4de8eceda87a17fa5b and data API 28423762e8cc3faae978e770899834b41e7cde99. The bounded company-selector amendment is accepted, 10/10 tasks. Local acceptance and publication verification retain separate scope. Its immutable pair remains in the historical publication record.

For alpha-42188370167-1, on 2026-11-06 the owner reported successful Linux docker compose pull and docker compose up -d --no-build, healthy data API startup, retained dashboards and working company autocomplete. This closes the owner-reported deployment check for that update. It is not independent server inspection, a claim that all widgets passed, or backup/restore acceptance.

Previous financial-input release

alpha-41030227140-1 was built from QOpenBB 6cca7e40c7e9830546b7051dc36995902acede35, Workspace c652b909627d7634241eee2ed13a561fbb4f177b and data API 28423762e8cc3faae978e770899834b41e7cde99. Both CI jobs, three public release assets and six anonymous digest, release-tag and latest pulls passed. Initial financial-input batch: 26/26; broader provider families remain follow-on work.

Service Exact published reference
workspace ghcr.io/norandom/qopenbb-workspace@sha256:b40a2472b3a5f6ca325aa126b7a2131aa517dc1a622f4f1a3a7cae24f105f269
data-api ghcr.io/norandom/qopenbb-data-api@sha256:743b9fd657e8e2e8346a42fb8b3f8146b49ebf134987ffcd6363c879ffc5e6d1

The release manifest binds the pair to its sources. Publication acceptance records public pulls and the isolated published-data-image catalog probe. Local Income acceptance covers visible FMP values across companies/periods, missing-input recovery, refresh and save/reopen. Live input acceptance supplies the separate FMP/FRED source comparison. These do not establish CI Workspace browser execution, the owner's deployment or recovery.

The prior alpha-40689838352-1 introduced native uv, readable Python and Valkey; its runtime and publication evidence remains historical. The owner reported that prior alpha up on 2026-10-28. That report does not transfer server acceptance to the current pair. See the first-spec closure.

Earlier prototype repair

The first-login GET now returns HTTP 200 with JSON null when no developer questionnaire exists, preserving the ordinary onboarding flow and saved answers. The data image packages and serves the existing widgets.json and apps.json. Optional external app preview URLs are omitted so Workspace uses its existing fallback. That earlier catalog contained FMP company profile/income and FRED series; the current eleven-definition catalog preserves those baseline IDs. See the onboarding source review, catalog source review and preview repair review.

Fixed GET /agents.json returns HTTP 200 with an empty array, truthfully advertising that the data backend has no configured agents. It preserves the Workspace discovery contract without introducing AI functionality; Anthropic remains in its separate spec. See the agent-discovery review.

Earlier assembled runs exposed the missing catalog, external FRED preview and agent-discovery 404 responses. They remain failed evidence. CI run 40467871625 published the four repairs together. The final fresh-account browser journey passed in 21.1 seconds on that exact published pair: onboarding returned HTTP 200/null; the starter displayed annual AAPL revenue of 416,161,000,000 USD for period ending 2025-09-27, matching the actual response and refresh; later login bypassed onboarding. First-session and later-session diagnostic arrays were empty. See the independent application review and application result.

  • Verify the repaired release assets and both public image identities, including all six anonymous pulls.
  • Complete the isolated published-image Compose journey: first login, installed annual AAPL income widget, displayed identity/date/currency/revenue, refresh and strict diagnostics.
  • Complete the pull-only local installation rehearsal.
  • Receive owner confirmation that the deployed alpha is up (2026-10-28); detailed host inspection is not claimed.
  • Verify the generic-widget empty-required-symbol guard. Broader providers, analyst persistence and backup/restore remain separate obligations.

Build and publication

bash pipeline/ci.sh check runs maintained-scope complexity checks and focused delivery tests. bash pipeline/ci.sh build --output NEW_DIRECTORY --release-version alpha-ID builds both services serially through Dagger and records their inspected and loaded identities. Dagger builds images only.

After a successful build, the portable publication command is:

pipeline/.venv/bin/python -m qopenbb_ci.alpha_cli \
  --build-output artifacts/ci-candidate \
  --registry-namespace ghcr.io/norandom \
  --manifest artifacts/alpha-release/manifest.json

It publishes unique alpha tags for both services, verifies their remote identities and shared source revisions, then updates latest. It writes a completed manifest only when both aliases match. Updating two registry tags is not atomic: a failed second update can leave mixed aliases. Use the pair of exact references in a completed release manifest to reproduce an alpha.

GitHub Actions runs checks for PRs and ordinary main pushes. After a reviewed feature milestone passes its real-data acceptance, dispatch gh workflow run prototype.yml --ref main -f build_images=true once for the set of commits. The main-branch dispatch builds both images, publishes them and creates a tagged prerelease. See installation.

Publishing a prerelease manually on GitHub also builds both images through Dagger from that release's tagged QOpenBB commit and its pinned application sources. Use a commit containing the updated workflow. Successful publication attaches manifest.json, compose.yaml and default.env.sample to the existing release, preserving its notes. The immutable image version remains alpha-RUN_ID-ATTEMPT; the manifest additionally identifies the GitHub release tag and QOpenBB commit. Both verified images receive latest aliases. Stable releases and ordinary pushes do not publish images.

Publication jobs share a concurrency group to avoid simultaneous latest promotion. GitHub concurrency is not an unlimited release queue; wait for one publication to finish before submitting another. A failed build does not establish available release images. Workflow-created prereleases already follow a successful build and do not recursively trigger another workflow through GITHUB_TOKEN.

  • Verify prerelease event selection, tagged checkout and existing-release asset upload with focused tests and independent review.
  • Verify the first manually published prerelease through the hosted build/publication path.

CodeQL runs separately from image delivery; see security scanning for language coverage and scan status.

Acceptance boundary

Radar Line/Area are accepted in the ordinary Table/File journey on application source af226971c53922de5925d9b068fbfbd81df02527 and local image sha256:da46760094b602464e9adefa6caae2b100f34307a486076fa9cec4625125a760. Both retained-FMP family tests pass, including financial geometry, controls, refresh, fresh reopen, PNG export and observed candidate diagnostics. The owner approved the pictured appearance. CI run 40086673952 rebuilt test-only source 194691e589ad75afb74d227574402dfb43ba6aea; publication assets and six anonymous pulls pass. This does not establish browser execution of the CI image bytes, assembled Compose acceptance or owner-server deployment. See Radar verification.

The following Range and Box Plot records describe earlier releases.

Range Bar/Area are accepted in the ordinary Table/File journey on Workspace e2b87ed98cd5ef18fb9ca6ddf888802d71fc685e and local packaged image sha256:1ff9d136027b0e0ae0f55b89f3faae5892602b2aeb3cee5482f408dc3a3bb0b0. Both retained-FMP journeys pass, including financial extrema, controls, navigation, refresh, fresh reopen and PNG export. The owner accepted default Area appearance; independent review verified corrected navigator spacing. Alpha-39920081345-1 publishes the same source after both CI jobs passed. Release assets, source pins and six anonymous image pulls are verified. These are separate local runtime and CI publication results, not browser execution against the CI image bytes. See Range verification. Assembled Compose and owner-server acceptance remain open.

The following Box Plot record describes an earlier release.

The owner accepted the Box Plot milestone in the ordinary Table/File journey. Two browser scenarios passed on Workspace da5979cb020af7737f9a76544ae527d8f2a30831 and local packaged image sha256:4b7c12f04ab7d5e254c5f0980b310569340f034fcd0b826adf6b495a57717025: retained-FMP five-number summaries in raw USD, synthetic edge cases, controls, themes/navigation, refresh, save/reopen and PNG export. The owner approved the original/replacement appearance and default miniature on 2026-10-22. CI run 39757904293 passed both jobs and published the same Workspace source; both service identities and six anonymous pulls were verified separately. The local browser result does not establish execution against the published CI image bytes. See Box Plot verification. Assembled Compose and owner-server acceptance remain open. Unfinished renderer families/callers, provider, persistence, AI and Excel work belongs to successor specs in the roadmap.

The previous pie/donut release retains its acceptance evidence.

The earlier CI failure occurred after Workspace export, in engine identity verification. The repair resolves the pinned image through Docker instead of equating a local image ID with a registry manifest digest. Focused tests cover both Docker storage representations; the hosted run now confirms the repaired build outcome.

Earlier tool rejections prevented automatic local runtime startup. The owner subsequently started the identified combination-chart candidate, allowing its recorded browser acceptance; those results do not imply acceptance of other candidates or deployment environments.