You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Examples: feat: add new SDK method · feat(storage): support file uploads · feat!: breaking API change
Description
Added secrets to SDK, along with examples and tests.
Motivation
Changes
Testing
Unit tests added
Integration tests added
Smoke Tests added/updated
Tested locally
Breaking Changes
Checklist
PR title follows Conventional Commits format (feat: or feat(scope):)
Documentation updated (if needed)
Breaking changes documented (if applicable)
CodeAnt-AI Description
Add first-class Secret support and devbox integration (create, inject, verify, delete)
What Changed
SDK exposes Secret as an object and a new secret operations surface (create, update, list, delete, fromName) so callers can manage secrets via object-oriented APIs
Devbox creation now accepts secrets (Secret objects or names) and MCP/gateway specs can receive Secret objects so secrets are injected into devboxes as environment variables
Examples, smoketests, and docs added/updated: new example shows creating a secret, injecting it into a devbox, verifying access, updating and deleting; smoketests cover secret lifecycle and devbox integration
Impact
✅ Shorter secret setup for devboxes ✅ Fewer manual API calls to inject secrets ✅ Clearer secret lifecycle verification in examples and tests
💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
@codeant-ai ask: Your question here
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
@codeant-ai ask: Can you suggest a safer alternative to storing this secret?
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
@codeant-ai: Your feedback here
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
@codeant-ai: Do not flag unused imports.
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
@codeant-ai: review
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.
Hardcoded Secret The example commits concrete secret values into source (both initial and updated values). Hardcoded secrets in examples can be accidentally committed to VCS or leaked in logs; they should be provided from environment or generated dynamically for tests.
Plaintext secrets in devbox test The devbox-integration test injects a plaintext secret ('secret-for-devbox-test') and asserts it appears in the devbox environment. Ensure CI logging and test artifacts cannot leak this value, and confirm tests run in isolated environments.
Plaintext secrets in tests Tests create secrets using hard-coded plaintext values (e.g. 'test-secret-value'). These values can be recorded in CI logs or artifacts. Consider generating secrets dynamically from env or ensuring logs are redacted.
Inefficient lookup getInfo() lists up to 5000 secrets then does an in-memory find by name. This is inefficient and fragile for large accounts (could miss secrets if >5000) and will be slower than a direct lookup or server-side filter. Consider using a dedicated get-by-name endpoint or server filtering/pagination.
Secret resolution The helper resolveSecretName assumes a Secret object always has a name property and returns it directly. If the Secret shape changes or an object missing name is passed, callers will receive undefined (or a runtime error if later used). Validate/fallback or throw early to avoid sending invalid names to the API.
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
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.
codeant-ai
Bot
added
the
size:XL
User description
Format:
feat[optional scope]: <description>Examples:
feat: add new SDK method·feat(storage): support file uploads·feat!: breaking API changeDescription
Added secrets to SDK, along with examples and tests.
Motivation
Changes
Testing
Breaking Changes
Checklist
feat:orfeat(scope):)CodeAnt-AI Description
Add first-class Secret support and devbox integration (create, inject, verify, delete)
What Changed
Impact
✅ Shorter secret setup for devboxes✅ Fewer manual API calls to inject secrets✅ Clearer secret lifecycle verification in examples and tests💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.