Claude Code has released version 2.1.143, bringing significant improvements to plugin management and session handling. This update enforces plugin dependencies, ensuring that disabling a plugin doesn't disrupt others that rely on it. Additionally, users can now view projected context costs in the plugin marketplace. Background sessions have been enhanced to retain model and effort settings after waking from idle, and PowerShell tools are now enabled by default for specific users. These updates aim to enhance user experience and operational reliability.
Read original
© The AI Daily BriefCursor has introduced a more affordable coding model aimed at developers.
© GitHub Changelognpm has introduced staged publishing and new install-time controls in its latest update, aiming to bolster supply-chain security. Staged publishing allows package maintainers to approve prebuilt tarballs before they become publicly available, adding a layer of human verification. This feature is particularly beneficial for CI/CD workflows, ensuring that only trusted packages are released. Additionally, new install source flags provide developers with more control over dependency sources, enhancing security by allowing explicit permissions for file, remote, and directory installs. These updates mark a significant step towards more secure package management in the npm ecosystem.
© GitHub ChangelogGitHub has introduced a public preview of issue fields for all organizations, offering a new way to manage and track issues across repositories. This feature allows organizations to define typed metadata like Priority and Effort, which automatically appear on every issue, simplifying workflows and reducing the need for manual syncing. With support for single select, text, number, and date types, these fields can be integrated into project views and automated via APIs. This update is particularly beneficial for large enterprises and open source projects, providing a structured alternative to complex label systems. By adopting this feature, teams can enhance their automation capabilities and maintain consistent field values without manual intervention. GitHub plans to continue refining the feature based on user feedback, ensuring it meets the evolving needs of its users.