Skip to content

release: 0.3.0 - #131

Open
tarannum-2002 wants to merge 17 commits into
mainfrom
release-0.3.0
Open

tarannum-2002 wants to merge 17 commits into
mainfrom
release-0.3.0

Conversation

@tarannum-2002

Copy link
Copy Markdown
Contributor

Everything on release-0.3.0 that main does not have: 17 commits, 136 files. main is not ahead, so nothing is lost.

What

  • Decision support system. charts/decision-support-system 0.1.0 to 0.2.0, matching what DSS v0.2.0 reads: the model gateway, provider preferences, place search, schemes, redaction and translation settings, and traces.
  • Photon. A new charts/photon, the place search DSS uses for names it does not know.
  • Experience. New charts/experience-api and charts/experience-ui, the chat API and its web client.
  • One chart per product. charts/langfuse 2.2.0 to 3.0.0 now carries its own Postgres and MinIO. charts/lite-llm becomes charts/litellm 0.2.0, with its own Postgres.
  • API collection. bppId and bppUri and tidier environments (feat: add bppId and bppUri to the API collection and tidy its environments [#121] #124).

Why

Dev and staging deploy from main, so the DSS, Photon, Experience, Langfuse and LiteLLM Applications that infra-automation now has (#30, #31, #32) can only find their charts once this is released.

Testing

Relates to OpenAgriNet/engineering-tracker#233

nisargabd and others added 17 commits November 4, 2026 15:11
Publish catalogs now name the BPP that serves them, and every
transaction call (select, init, support, status) carries bppUri in its
context so the request can be routed to that BPP. Both come from
variables, never hardcoded hosts.
#121]

The quick-start registry runs with authentication_enabled=false and the
stack ships no Keycloak, so the token request could never succeed and
the Bearer header on the writes carried nothing.
The two local environments differed in only two adapter URLs, so one
API environment now covers single mode, with the multi-mode values in
the descriptions and README. The registry collection shares just
registry-host with it, so it gets its own file.

registry-token, schema-name, schema-url and ticket-no are dropped from
the environments: the scripts set them as collection variables, and an
environment value, even an empty one, shadows those, so the token and
ticket number never reached the next request.
…d status [#121]

Matches the PMFBY folders, which are already named after the action they call.
…#121]

The negative cases are not needed in the collection. The README request count is corrected to 38.
feat: add bppId and bppUri to the API collection and tidy its environments [#121]
feat: catch the DSS chart up with the app, and add a Photon chart
feat: add charts for the experience API and UI
feat: one chart per product, with everything it needs under it
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants