BUG CICD is not deploying changes to the back-end

[OperationalFallacy]

Before opening, please confirm:

• I have checked to see if my question is addressed in the FAQ.
• I have searched for duplicate or closed issues.
• I have removed any sensitive information from my code snippets and submission.

Amplify Hosting feature

Backend builds

Is your feature request related to a problem? Please describe:

I've made some changes to the backend/function, added custom policy.

Local amplify shows the changes pending. Pushed it to the env branch, build runs - and... nothing

Local amplify still shows pending changes to the functions.

version: 1
applications:
  - appRoot: xxx-website
    backend:
      phases:
        install:
          commands:
            - pwd
            - cd ../xxx-api
            - node --version
            - nvm use 18
            - nvm use 18.17.0 || true
            - node --version
            - yarn global add tsc-alias typescript tsc
        build:
          commands:
            - yarn install --production
            - amplify --version
            - cat $(which amplifyPush) || true
            - amplifyPush --simple

Builds logs show changes to the resources

UPDATE_IN_PROGRESS                  functionXxx AWS::CloudFormation::Stack Fri Jan 12 2024 14:04:46 GMT+0000 (Coordinated Universal Time)

Build configured with Linux2023 image.

Describe how you'd like this feature to work

After the build, local amplify should not have any changes pending, right?!

[github-actions]

This has been identified as a feature request. If this feature is important to you, we strongly encourage you to give a 👍 reaction on the request. This helps us prioritize new features most important to you. Thank you!

[mauerbac]

I'm sorry for the delay. Closing this as we've made changed here and this is an old issue

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.