AEM Version Updates - Automatic Updates - Handle custom code pushed to Staging but not Production

[#1]

Request for Feature Enhancement (RFE) Summary:	Ensure AEM Maintenance Update releases respective code artifacts to Stage and Production Environments
Use-case:	We currently do Stage deployments on a weekly basis and Production deployments on bi-weekly basis. However, the AEM Maintenance Update pushes back the baseline code to last successful deployment for Production to Stage as well. This then requires another Stage. Ideally as the pipeline is able to pick up the last commit id of the deployment to Production, it should also be able to pick up the Commit Id of Stage and deploy the necessary artifacts. This deviates from the usual principle of deploying same artifacts on Stage and Production but helps to keep the system in as-is state before and after Maintenance Updates.
Current/Experienced Behavior:	The custom code that was only available on Stage gets lost and has to be deployed again.
Improved/Expected Behavior:	The Production instance should have the last known production deployment artifacts while the Stage instance should similarly have its last deployed artifacts to ensure continuity.
Environment Details (AEM version/service pack, any other specifics if applicable):	AEMaaCS (AEM Release - 2023.12.14538.20231205T165334Z)
Customer-name/Organization name:	TA Digital
Screenshot (if applicable):	AEM Version Updates | Adobe Experience Manager
Code package (if applicable):	N.A

[#2]

@Rohan_Garg 

Thanks for proposing this idea

This has been reported to the engineering under the internal reference SITES-18667. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.