Skip to content

feat: automate sandbox version updates in documentation#155

Open
hittyt wants to merge 8 commits intoalibaba:mainfrom
hittyt:docs/align-code-interpreter-version
Open

feat: automate sandbox version updates in documentation#155
hittyt wants to merge 8 commits intoalibaba:mainfrom
hittyt:docs/align-code-interpreter-version

Conversation

@hittyt
Copy link
Collaborator

@hittyt hittyt commented Feb 1, 2026

Summary

  • Introduced 'sandboxes/code-interpreter/VERSION' as the single source of truth.
  • Added 'scripts/manage_sandbox_version.py' to automate version updates in docs/examples while preserving 'latest' in tests.
  • Updated '.github/workflows/manual-docker-publish.yml' to auto-trigger doc updates on release.
  • Added '.github/workflows/verify-sandbox-version.yml' as a CI gatekeeper.
  • Aligned existing documentation to v1.0.1.

Testing

  • Not run (github ci config)
  • Unit tests
  • Integration tests
  • e2e / manual verification

Breaking Changes

  • None
  • Yes (describe impact and migration path)

Checklist

  • Linked Issue or clearly described motivation
  • Added/updated docs (if needed)
  • Added/updated tests (if needed)
  • Security impact considered
  • Backward compatibility considered

@hittyt hittyt force-pushed the docs/align-code-interpreter-version branch from 0c4737e to df10828 Compare February 1, 2026 08:50
# For multi-architecture builds (requires Docker Buildx)
docker buildx build --platform linux/amd64,linux/arm64 \
-t opensandbox/code-interpreter:latest .
-t opensandbox/code-interpreter:v1.0.1 .
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should not modify locally Docker-built image to any release version.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

chmod +x build.sh
./build.sh

- name: Update Code Interpreter Version in Docs
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to support dynamic updates for all components, including components such as execd and egress?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Refactored update components logic

@Pangjiping Pangjiping added the documentation Improvements or additions to documentation label Feb 1, 2026
@hittyt hittyt force-pushed the docs/align-code-interpreter-version branch 3 times, most recently from 4500144 to ef151ae Compare February 1, 2026 11:07
- Introduced 'sandboxes/code-interpreter/VERSION' as the single source of truth.
- Added 'scripts/manage_sandbox_version.py' to automate version updates in docs/examples while preserving 'latest' in tests.
- Updated '.github/workflows/manual-docker-publish.yml' to auto-trigger doc updates on release.
- Added '.github/workflows/verify-sandbox-version.yml' as a CI gatekeeper.
- Aligned existing documentation to v1.0.1.
@hittyt hittyt force-pushed the docs/align-code-interpreter-version branch from ef151ae to 0bc4b77 Compare February 1, 2026 11:12
@hittyt hittyt requested a review from Generalwin as a code owner February 1, 2026 11:12
@hittyt hittyt requested a review from Pangjiping February 1, 2026 11:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants