Blog

Node.js v25.1.0 shipped on 2025-10-28. This release includes 269 commits with several notable changes such as the addition of the ‘optimizeEmptyRequests’ server option in the HTTP module, which can enhance performance by optimizing requests with no body. Furthermore, it introduces a new watch config namespace in the source and expands the SQLite module by allowing the setting of a defensive flag.

• Feature: HTTP module now includes the optimizeEmptyRequests server option, enhancing performance for empty requests.
• Feature: New watch config namespace added for improved configuration management.
• Feature: SQLite module can now have a defensive flag set for increased security.

• optimizeEmptyRequests server option: Improves performance for empty HTTP requests, reducing unnecessary overhead.
• Watch config namespace: Provides better configuration management for developers using Node.js, allowing for more organized code.
• Defensive flag in SQLite: Enhances security and reliability of database interactions by providing additional safeguards.

• No known issues reported in official notes.

Source: GitHub

Node.js v25.1.0 shipped on 2025-10-28. This release includes 269 commits with several notable changes such as the addition of the ‘optimizeEmptyRequests’ server option in the HTTP module, which can enhance performance by optimizing requests with no body. Furthermore, it introduces a new watch config namespace in the source and expands the SQLite module by allowing the setting of a defensive flag.

• Feature: HTTP module now includes the optimizeEmptyRequests server option, enhancing performance for empty requests.
• Feature: New watch config namespace added for improved configuration management.
• Feature: SQLite module can now have a defensive flag set for increased security.

• optimizeEmptyRequests server option: Improves performance for empty HTTP requests, reducing unnecessary overhead.
• Watch config namespace: Provides better configuration management for developers using Node.js, allowing for more organized code.
• Defensive flag in SQLite: Enhances security and reliability of database interactions by providing additional safeguards.

• No known issues reported in official notes.

Source: GitHub

TypeScript v5.9.3 shipped on 2025-11-08 16:54:16. This release includes a recreation of the tag to point at the correct commit and fixed issues for versions 5.9.0, 5.9.1, and 5.9.3. Users can rely on the npm package containing the correct content, ensuring smoother development experiences.

• Feature: Recreation of the tag to point to the correct commit
• Feature: Fixes for issues in TypeScript 5.9.0, 5.9.1, and 5.9.3

• Correct commit reference: users can trust the integrity of the TypeScript package.
• Fixed issues from previous versions: enhances stability for projects relying on TypeScript.
• Availability of npm downloads: easy access for developers to integrate the latest TypeScript version.

• No known issues reported in official notes

TypeScript v5.9.3 shipped on 2025-11-08 16:54:16. This release did not introduce any new features, changes, or fixes, which may indicate a focus on stability or preparatory work for future updates. Users may want to monitor upcoming releases for new capabilities and improvements.

• Feature: No new features introduced
• Feature: No changes made
• Feature: No fixes applied

• No new features: Users will need to wait for future updates for enhancements.
• No changes: Stability remains a key focus for the development community.
• No fixes: Indicates a potential pause in addressing reported issues or bugs.

• No known issues reported in official notes

Node.js v24.11.0 shipped on 2025-10-28. This release marks the transition of Node.js 24.x into Long Term Support (LTS) with the codename ‘Krypton’, which will receive updates until April 2028. Aside from updating metadata, no additional changes were introduced compared to Node.js 24.10.0.

• Feature: Transition to Long Term Support (LTS) with codename ‘Krypton’
• Feature: Updated process.release object for consistent metadata

• Long Term Support designation: provides users with a stable version that will receive updates and support until April 2028.
• Updated process.release object: ensures consistent metadata for developers using the runtime.

• Known issue with Buffer.allocUnsafe returning zero-filled buffers instead of uninitialized memory; expected to be fixed in the next LTS release.

Docker v29.0.0 shipped on 2025-11-11. This release introduces several breaking changes, including the deprecation of the Go module github.com/docker/docker, which is now replaced by github.com/moby/moby/client and github.com/moby/moby/api. Users should take note of the experimental support for nftables and the removal of Docker Content Trust from the CLI, which may impact security workflows.

• Feature: The Go module github.com/docker/docker is deprecated in favor of github.com/moby/moby/client and github.com/moby/moby/api.
• Feature: Experimental support for nftables can now be enabled to enhance network security.
• Feature: Docker Content Trust was removed from the CLI, now requiring a separate plugin for trust management.
• Feature: cgroup v1 is deprecated; users should migrate to cgroup v2.
• Feature: Debian armhf packages now target ARMv7 CPUs.

• Breaking changes: Users must transition to the new public modules (client and api) or risk compatibility issues.
• Experimental nftables support: This allows users to leverage advanced firewall capabilities if enabled, enhancing network security.
• Removal of Docker Content Trust: Users will need to rely on a separate plugin for trust management, potentially complicating image verification processes.

• Several breaking changes that require careful review before upgrading.
• Docker Content Trust is removed from the CLI, which may affect security protocols.
• cgroup v1 is deprecated; users should migrate to cgroup v2 as soon as possible.

Docker v29.0.1 shipped on 2025-11-14. This release includes several bug fixes aimed at improving the usability and functionality of Docker commands. Notably, the docker image list command now respects the NO_COLOR environment variable, and a bug preventing the visibility of untagged images in docker image list –all has been resolved.

• Feature: docker image list now considers the NO_COLOR environment variable for choosing the colored output.
• Feature: Fix a bug causing docker image list –all to not show untagged/dangling images.
• Feature: Fix build on i386, enhancing compatibility for older architectures.

• NO_COLOR support: Users can now control colored output based on their environment settings, enhancing terminal readability.
• Untangled images visibility: Fixing the untagged images bug ensures users can better manage their images without missing unreferenced data.
• i386 build fix: This enhances compatibility for users running Docker on older architectures.

• No known issues reported in official notes.

Source

Node.js v25.1.0 shipped on 2025-10-28. This release includes 269 commits with several notable changes such as the addition of the ‘optimizeEmptyRequests’ server option in the HTTP module, which can enhance performance by optimizing requests with no body. Furthermore, it introduces a new watch config namespace in the source and expands the SQLite module by allowing the setting of a defensive flag.

• Feature: HTTP module now includes the optimizeEmptyRequests server option, enhancing performance for empty requests.
• Feature: New watch config namespace added for improved configuration management.
• Feature: SQLite module can now have a defensive flag set for increased security.

• optimizeEmptyRequests server option: Improves performance for empty HTTP requests, reducing unnecessary overhead.
• Watch config namespace: Provides better configuration management for developers using Node.js, allowing for more organized code.
• Defensive flag in SQLite: Enhances security and reliability of database interactions by providing additional safeguards.

• No known issues reported in official notes.

Source: GitHub

TypeScript v5.9-rc shipped on November 8, 2025. This release serves as a release candidate, indicating that it is close to the final version and includes a series of bug fixes and improvements based on user feedback. Developers can begin testing this version to prepare for the stable release, which is crucial for ensuring compatibility and stability in their projects.

• Feature: Release Candidate status allows early testing.
• Feature: Numerous bug fixes enhance overall stability.
• Feature: Community feedback incorporated for better alignment with user needs.

• Release Candidate Status: Allows developers to test upcoming features and fixes before the official release.
• Bug Fixes: Addresses numerous issues from previous versions, improving overall stability.
• Community Engagement: Feedback from the community has been incorporated, ensuring that the release aligns with user needs.

• No known issues reported in official notes.

Chrome v144.0.7523.2 shipped on 2025-11-14. This update for Chrome Dev on Android brings minor updates without significant changes or new features specified. Users can download the latest version from Google Play to ensure they are running the most up-to-date build of the browser.

• Feature: Chrome Releases: Chrome Dev for Android Update
• Feature: CHROME DEV FOR ANDROID UPDATE

• No new features specified: Users should check for performance improvements or bug fixes, although none were explicitly listed.
• Minor updates: Regular updates help maintain security and performance standards.

• No known issues reported in official notes.