Serverless-Next.js deployment not updating the EdgeLambda version to latest in Cloudfront cache behaviour mapping

[dnaveen61]

While deploying the serverless-next.js component via pipeline, its not updating the Server side rendering EdgeLambda function version to the latest version in Cloudfront cache behaviour(Public assets- js/*) route path.

But for other _next/* and static/* routes the lambda mapping is being updated with correct latest version.

After deployment eventhough the edgelambda has been published with new version, but still cloudfront lambda association is still having old version. This resulted in issues like the routes for public assets available to be missing for resources like js/results.js
(because an older version of the nextjs lambda app did not have this route/resource added yet).

Still the lambda version is showing as 653 in mapping though latest version is 963.

To fix this we are doing the mapping update manually to the latest version. Please let know any findings to fix this issue.

[robertsonsamuel]

@dnaveen61 out of curiosity. I'm on 3.7.0.
Are you sure the functions are mapping versions 1:1 ?

For example my api/* route follows the version correctly and is named Lambda@Edge for <app name> (API). If I check that edge function version in cloud-front it matches.

Curious if this is an alpha 11 issue of course. I can at least say I'm not seeing that on my production version on 3.7.0.

Can totally be valid, but that threw me off as version numbers may look off, but were actually correct once I looked again.