Yesterday's Top Poster

Industry News

We’ve made a small but meaningful update to how deployment statuses are displayed in the Netlify UI. Previously, when a site was deployed from a partner site (such as Bolt, for example), the label simply read "Manual deploy." Now, you’ll see "Deployed from [Partner name]" instead. This change helps provide clearer visibility into where your deployments are coming from, making it easier to track automated workflows and integrations. If you’re working with partners like Bolt, this update ensures your deployment history reflects that connection, reducing ambiguity and improving collaboration. It doesn’t change anything about how deployments work—just a small tweak to make things clearer and more informative. Let us know if you have...
Netlify now provides official AI context files to improve the accuracy and reliability of AI coding assistants like Cursor, Windsurf, and GitHub Copilot. Developers can easily integrate the context files into their projects, with specific support for Cursor and other AI tools. Additionally, Netlify CLI (v18.1.0+) includes a netlify recipes ai-context command for seamless context management, allowing for easy updates while preserving custom overrides. With this realease, Netlify’s documentation also now supports a /llms.txt resource, enabling AI tools that automatically reference https://docs.netlify.com/llms.txt to have enhanced web context. To learn more about this and how to use it, check out our documentation. Continue reading...
Previously, users creating sites through partner tools or AI code generation tools like Bolt had to manually enable form detection—often causing confusion and blocking access to submissions. Now, form detection is autoenabled, allowing end users, especially low-code users, to start collecting submissions immediately without extra setup. This update reduces friction for both partner tool users and AI-generated site deployments, ensuring a smoother experience. Continue reading...
Netlify UI settings to deploy all branches with the prefix release We now support configuring your site to deploy all branches with a specific prefix. Leverage the new functionality by configuring Branch Deploys in Site Configuration > Continuous deployment. Add a wildcard at the end of your prefix to deploy all branches beginning with the given text - for example, enter release/* to automatically deploy release/alpha-1, release/v2, and so on. Continue reading...
Back
Top