v0.1.4

What's Changed

• feat: --skip-resource-checks flag by @zpg6 in #7
• fix: upsert resource group instsead of always attempting create by @zpg6 in #8

Full Changelog: v0.1.3...v0.1.4

v0.1.3

[0.1.3] - 2025-11-03

Added

• Health check now validates static asset cache headers are configured correctly.
• Health check now performs HTTP request to verify Function App is responding (with response time).
• Added image optimization support using Azure Blob Storage as cache and sharp for processing.

Fixed

• Static assets on Azure Blob Storage now have proper cache-control headers (_next/static files have immutable with 1-year cache, other assets have must-revalidate).
• Static asset redirects now conditionally set cache headers based on file path (only _next/static files get immutable cache).
• _next/data files are no longer redirected to blob storage, allowing proper ISR cache handling through the function app.
• CSS files are now patched during deployment to include /assets container path in font URLs, fixing 400 errors for fonts referenced in stylesheets.
• View logs quick action now recommends using npx opennextjs-azure@latest tail to access live logs in the Azure Portal.

Full Changelog: v0.1.2...v0.1.3

v0.1.2

What's Changed

• feat: cli health cmd by @zpg6 in #1
• feat: cli delete command by @zpg6 in #2

Full Changelog: v0.1.1...v0.1.2

Allows for better testing:

1. health: All 10 checks passed on existing deployment
2. delete: Resource group deleted successfully (waited for completion)
3. build: Next.js app built successfully
4. deploy: App redeployed successfully (same resource group name reused)
5. health: All 10 checks passed on fresh deployment

v0.1.1

[0.1.1] - 2025-10-29

Initial Release!

Added

• CI workflow for building library.
• CI workflow for building example application.
• Application Insights integration for logs and monitoring.
• Log stream quick access from CLI via tail command.
• Auto-registration of Microsoft.AlertsManagement resource provider.
• Basic example application demonstrating usage.
• README and LICENSE documentation.
• Documentation on Azure resources used by the project.
• Documentation noting Application Insights as default monitoring solution.
• Instructions for how basic-app example was generated.

Fixed

• .open-next folder now properly cleaned on each build.
• Bundler issues with console.error statements.
• Bicep template synchronization during deployment.
• Relative paths for configuration imports.
• create-next-app usage must avoid using turbopack flag.
• Stream handling now properly awaited.

Full Changelog: https://github.com/zpg6/opennextjs-azure/commits/v0.1.1