Merged
Conversation
Enable self-hosted Kubernetes deployments as an alternative to docker-compose. The chart packages all Agenta OSS components (API, web, services, workers, cron, Redis, SuperTokens, PostgreSQL) with Bitnami PostgreSQL as a subchart dependency, Alembic migrations as a pre-install/pre-upgrade hook, and an optional ingress resource. Includes a CI workflow to publish the chart to GHCR on changes.
- Fix appVersion to use v-prefixed tag (v0.86.8) matching GHCR images - Add HOSTNAME=0.0.0.0 to web deployment so Next.js binds to all interfaces - Change runAsNonRoot default to false (images currently run as root) - Document PostgreSQL secret name dependency on release name - Document ingress className default (traefik) with override instructions
The ingress template previously hardcoded Prefix paths which only work
with Traefik. NGINX Ingress Controller requires regex capture groups
and ImplementationSpecific pathType for rewrite-target to work.
Add ingress.paths.{api,services,web} to values.yaml so users can
override path patterns and pathType per backend. Defaults remain
Prefix (backward compatible with Traefik). Update docs with the
full nginx configuration including path overrides.
When users provide a pre-created Kubernetes Secret via secrets.existingSecret, the Bitnami PostgreSQL subchart silently fails to find the password unless global.postgresql.auth.existingSecret is also pointed at the same secret. This adds a fail-fast validation template and clearer NOTES.txt guidance so users get an actionable error at install time instead of a broken deployment.
The pgauth secret name was hardcoded to "agenta-pgauth", requiring manual overrides when installing with a release name other than "agenta". By switching to a Go template expression evaluated via tpl(), the secret name automatically adapts to any release name. This also converts the pgauth secret to a pre-install/pre-upgrade hook so it exists before the Bitnami PostgreSQL subchart needs it, and removes the now-unnecessary documentation warning about release name mismatches.
The test pod would fail to render when api, web, and supertokens were all disabled since it produced an empty container spec. Wrapping the entire template in a conditional ensures the pod is only created when at least one testable service is enabled.
The container image uses supercronic for cron scheduling, not the traditional system cron daemon. This aligns the helm chart with the actual entrypoint and process name so the container starts correctly and the liveness probe checks the right process.
The Bitnami PostgreSQL subchart ignores auth.password when existingSecret is configured. The pgauth secret created by the chart sources the password solely from secrets.postgresPassword, making the extra --set flag a no-op that misleads users into thinking both values are required.
Add planning workspace documenting the root cause and fix for the registry page commit failure after hard refresh. The frontend incorrectly routes commits through the legacy endpoint when playgroundNodesAtom is empty.
Refine the registry commit bug plan after review to keep the first implementation scoped to the broken commit flow. Defer create and delete follow-ups until their refresh behavior is reproduced.
Removed community topics section and adjusted related content.
dosubot
bot
added
the
size:S
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Update README
Third-party packages (e.g. litellm >=1.82) can print diagnostic messages to stdout on import, which pollutes the path captured by the verify-SDK step and causes the case-match against /app/sdk/* to fail. Redirect stderr and pipe through tail -1 so only the final printed line (agenta.__file__) is captured.
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>
fix(ci): harden SDK path verification against stdout noise
…to fix/input_keys
Contributor
Author
Railway Preview Environment
Updated at 2026-03-12T10:43:21.721Z |
- runnableBridge.isDirty now only checks the molecule that owns the entity (has data for it), avoiding false positives from probing all types - legacyAppRevision isDirty returns false when server data not yet loaded instead of prematurely reporting dirty - workflow isDirty formatting cleanup (no logic change)
…only Remove unused commit logic that was moved to playgroundController. Keep only the revision polling utilities (newestRevisionForVariantAtomFamily, waitForNewRevision) used by createVariant flow.
…port Remove unused legacy commit logic. Keep only the variant modal adapter with runnableBridge-based commit context for EntityCommitModal.
…ontroller Clean up dead code paths that were superseded by workflow-based commits. The controller now uses commitWorkflowRevisionAtom and createWorkflowVariantAtom from the workflow entity module.
…EntityBridge Also remove unused imports from CommitVariantChangesModal.
Align exports with simplified commit.ts - remove references to deleted commit logic while keeping polling utilities and molecule API.
fix(frontend): sync prompt input keys in workflow drafts
Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
…ub-automation feat(docs): add deployment webhooks and GitHub automations
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
[Plan] fix(frontend): Registry commit fails after hard refresh
mmabrouk
approved these changes
Mar 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New version v0.94.1 in