Mike Nomitch

Initial pass at Container class

Refactoring

Some minor tweaks (#23150) * Adds Containers docs * A variety of tweaks to containers docs * Fixes bad links * replace icon * remove extra file * Apply suggestions from code review Various small fixes Co-authored-by: Nikita Sharma <54369599+nikitassharma@users.noreply.github.com> * Removes unnecessary pre-req and wrong TCP statement * Apply suggestions from code review Co-authored-by: Brendan Irvine-Broque <birvine-broque@cloudflare.com> * Apply suggestions from code review * Update pricing docs, make sure to clarify what is part of Workers Paid plan * Various tweaks --------- Co-authored-by: kodster28 <kody@cloudflare.com> Co-authored-by: Nikita Sharma <54369599+nikitassharma@users.noreply.github.com> Co-authored-by: Brendan Irvine-Broque <birvine-broque@cloudflare.com>

Python documentation additions and cleanup (#26267) * Python documentation additions and cleanup * Update minor typo in Python Workflows docs * Updates per feedback * Adding pywrangler link

Temporarily throwing errors based on retry count and not time or abort signal - Surfaces error better - Does not autostart a container in constructor, so we can throw error nicely Generally working though hacky Update error response Tweaks

Containers and Sandboxes beta removal (#29668)

Add custom token support to exposePort for stable preview URLs (#329) * Add custom token support to exposePort for stable preview URLs Allows users to pass a custom token to exposePort() to maintain consistent preview URLs across deployments and container restarts. This solves the issue of URLs breaking when sandboxes are restarted during deployments, enabling stable URL sharing in production. Token validation ensures 16-character length and URL-safe characters (lowercase letters, numbers, hyphens, underscores) matching the existing routing pattern. Backward compatible - tokens are optional and auto-generated if not provided. Includes comprehensive unit tests for validation logic and custom token usage. * Remove 16-character limitation for custom tokens Update token validation to accept variable-length tokens (1-63 chars) instead of fixed 16-character requirement. This provides more flexibility for users to choose meaningful token names while maintaining DNS subdomain compatibility. Changes: - Updated validateCustomToken() to check 1-63 char range - Updated request-handler regex to accept variable-length tokens - Updated all documentation and JSDoc comments - Updated unit tests to cover variable-length tokens - Updated changeset with new token length requirements * Set maximum token length to 16 characters Update custom token validation to enforce a maximum of 16 characters to match the auto-generated token length and ensure consistency. Changes: - Updated validateCustomToken() to check 1-16 char range (was 1-63) - Updated all JSDoc comments to reflect 1-16 char requirement - Updated interface documentation in ExposePortRequest - Updated unit tests to verify 16-char maximum - Updated changeset with corrected token length * Address PR feedback: Fix validation ordering and add token collision prevention Critical fixes: - Move token validation before container API call to prevent invalid tokens from reaching the container - Add token collision check to prevent multiple ports using same token - This fixes security vulnerability where wrong ports could be accessed Additional improvements: - Add test for token collision prevention - Add test for custom token storage verification - Add test for re-exposing same port with same token (valid scenario) - Update comment in request-handler.ts for clarity on token length All feedback from Claude Code Review has been addressed. * Fix empty token validation and clean up token handling Empty string tokens were bypassing validation because the truthiness check treated '' as falsy. Changed to explicit undefined check. Also removed token from container API since the container never used it, consolidated verbose unit tests into focused ones, and added E2E test coverage for custom token port exposure. * Remove misleading constant-time comparison comment * Use timing-safe comparison for token validation The standard === operator can leak token contents through timing differences. While not practically exploitable over the network, using crypto.subtle.timingSafeEqual follows Cloudflare's recommended pattern for comparing secrets. * Remove redundant comments in token validation * Downgrade changeset from minor to patch --------- Co-authored-by: Naresh <naresh@cloudflare.com>

Adds new instance types to allowed list (#10844) * Adds new instance types to allowed list * Updating missing spots with container instances * Fixing container instance type name tests and one flipped conditional * Adds changeset * Fixing another container test * Continuing to replace dev with lite * Continued changing of dev to lite * fixup changeset * warn about deprecated instance types --------- Co-authored-by: emily-shen <eshen@cloudflare.com>

Adds option to skip container rollout on deploy (#12656) Co-authored-by: emily-shen <eshen@cloudflare.com>

Adding changelog for node compat improvements (#19341) Adding changelog for node compat improvements and node API docs