Changelog

Follow up on the latest improvements and updates.

RSS

Nextjs-logo
We're thrilled to announce the launch of improved support for Next.js Incremental Static Regeneration (ISR) on Atlas.
What improvements does this release include?
In most cases, Next.js Incremental Static Regeneration (ISR) works as expected on Atlas - however, there are two issues:
  1. Traffic Spikes:
    When traffic spikes, new replicas of the application are spawned. These replicas mirror the version of the application that was originally built, which includes statically generated content that may now be outdated.
  2. Low Traffic Periods:
    Conversely, if a site receives no traffic for an extended period, the application scales down. When traffic picks up again, the initial visitors encounter this outdated content. This content isn’t cached; instead, it initiates a background revalidation process. After this process is complete, any subsequent requests will receive the freshly updated content, which is then cached.
Our solution for ISR support effectively addresses both issues, ensuring your site always displays the most recent content, regardless of traffic patterns. If your sites use Next.js Incremental Static Regeneration, we recommend using
@wpengine/atlas-next
package to ensure your content is going to be up to date regardless of the traffic patterns to your sites.
Does that mean Atlas supports on-demand Incremental Static Regeneration now?
Currently, on-demand ISR is not supported on Atlas. However, our team is actively working on adding this feature to our platform. Once it’s available, the use of the
@wpengine/atlas-next
package will be required to enable on-demand ISR on Atlas.
In the meantime, we are excited to offer our users the opportunity to start utilizing this enhanced functionality on their headless WordPress websites.
How can I get started?
Make sure to check our documentation for detailed onboarding information.
Feedback
Should you have any feedback, please submit it using the our feedback form.
node
Following the official Node.js release dates, we’re ending support for Node.js version 16 on Atlas, effective May 6th, 2024. This decision allows us to focus our resources on supporting newer versions of Node.js, which include critical security updates and performance improvements.
What This Means for You
If your applications or projects currently use Node.js version 16, they will continue to function without interruption. However, beginning on May 6th, any new builds of your Atlas applications set to utilize Node.js version 16 will not succeed. To avoid this issue, you'll need to upgrade your site to Node.js version 18 or newer.
Recommended Actions
We strongly encourage you to upgrade to one of the newer versions of Node.js supported on Atlas as soon as possible. This will ensure your applications can be updated seamlessly.
  1. Review your applications: Check your applications for any dependencies that might be affected by this change and plan your upgrade path accordingly.
  2. Test your applications: After upgrading, thoroughly test your applications to ensure they operate as expected without any issues.
Support and Resources
For the latest insights and updates, please ensure you visit our changelog regularly. It's your go-to source for detailed information on new features and improvements, helping you stay informed and maximize the benefits of our offerings.
We understand that this transition may require some adjustments, and we are here to assist you every step of the way. Our team of headless WordPress experts are available 24/7 to assist with any questions you may have.
Thank you for your understanding and cooperation as we make necessary enhancements to continue providing you with the best service possible. We appreciate your support and are excited to see your projects thrive on our platform.
Screenshot 2024-03-25 at 10
We're excited to announce the launch of our new Environment Variables Management Screen, a dedicated feature designed to simplify the management of your project's environment variables.
Key Features:
  1. Centralized Management:
    Add, edit, and delete environment variables effortlessly through a unified interface.
  2. Bulk Operations:
    Enhance efficiency with the ability to perform actions on multiple environment variables simultaneously—ideal for large-scale adjustments.
  3. Export Functionality:
    Easily export a file with your project's environment variables for backup or transfer purposes, ensuring you can manage these settings across different environments seamlessly.
  4. "Rebuild Needed" Alert:
    Our update introduces a clear notification system. Whenever you modify environment variables, you'll receive an immediate alert if a rebuild is necessary to apply the changes, ensuring you're always informed about the status of your environment.
This update reflects our commitment to improving your development workflow and user experience. Stay tuned for more UX updates in the upcoming weeks!
We're keen to hear your thoughts on this new feature. Share your feedback and suggestions on how we can further improve your platform experience via our feedback tool. Our team reviews all feedback suggestions immediately!
Happy coding!