Released: Jun 24, 2025

2025.2 での更新項目

機能

• Changes in the installation Helm chart - The CodeCanvas Helm chart was updated in 2025.2. The values.yaml file contains changes compared to 2025.1.4.
• Dev container now uses a non-root user - Starting with 2025.2, the default dev container image uses the codecanvas user (UID 22222, GID 22222) instead of root. The image includes sudo, so you can run commands with elevated privileges as needed. If your lifecycle or warm-up scripts rely on root access, review and update them to use sudo. Scripts that run as root may fail.
• Support for Cursor - You can now use the Cursor code editor in dev environments.
• Support for VS Code/Cursor extensions - You can now pre-install VS Code/Cursor extensions in dev environments by specifying the extension IDs in the dev environment template.
• Concurrent usage limits - CodeCanvas now lets you control how many dev environments users can run simultaneously. Each instance type has a usage cost, and each user has a usage limit.
• Support for Jupiter notebooks - Users can now run Jupyter notebooks in dev environments.
• Network policies for dev environments - The CodeCanvas operator Helm chart now supports basic network policies for dev environments. By default, inbound traffic to and between dev environments is blocked to improve isolation and security. Outbound traffic remains allowed, but chart parameters can change this behavior. You can also define custom network policies.
• Auto-disable warm-up and standby pool - To help reduce cloud costs, warm-up schedules and standby pools are now automatically disabled after repeated failures or inactivity. Namespace administrators can subscribe to email notifications when this happens.
• Skip scheduled warm-up if there are no Git changes - You can now configure the warm-up schedule to skip a warm-up run if there are no changes in the Git repository since the last warm-up.
• Default non-root user in dev containers - Dev environments now run under a non-root user by default. The codecanvas user (UID 22222, GID 22222) replaces root in the default container image. As a result of this change, the contents of dev environment and warm-up snapshots have also changed: instead of saving the /root directory, CodeCanvas now saves the /home directory where user data is stored.
• User activity per namespace and per template - You can now track user activity statistics not only globally, but also per namespace and per dev environment template. Each namespace and template now has its own User Activity page showing daily and monthly metrics for unique active users and the number of new dev environments.
• IDE plugin/extension availability check - When you specify a JetBrains IDE plugin or a VS Code/Cursor extension in a dev environment template, CodeCanvas now verifies that the plugin or extension exists in the corresponding marketplace (JetBrains Marketplace or VS Code Marketplace). Template change invalidates warm-up snapshot - If you change a dev environment template in a way that affects warm-up output (for example, by changing lifecycle scripts, environment variables, etc.), the existing warm-up snapshot becomes outdated. The UI now suggests re-running the warm-up to generate a new valid snapshot.