after bitbucket pipeline push to Heroku, Heroku overrides it with it's own process

[alexwonguhuru]

This is my config for the bitbucket pipeline for deploying to heroku 

image: node:7.8.0

pipelines:
  default:
    - step:
        script: # Modify the commands below to build your repository.
          - node -v
          - curl -o- -L https://yarnpkg.com/install.sh | bash -s -- --version 0.21.3
          - export PATH=$HOME/.yarn/bin:$PATH
          - yarn
          - git config --global push.default simple
          - git push -f https://heroku:$HEROKU_API_KEY@git.heroku.com/$HEROKU_APP_NAME.git

I have node 7.8.0 here, but after the `git push -f...` command, heroku starts installing it's own node (version 6), so I fixed it by updating my package.json to specify the node version in the engines object.

My question, is what is the point of setting up the pipeline to node 7.8.0 and yarn and all that, when after I push to heroku, heroku installs node and yarn anyways on its own. 

Thank you.

[Edwin Kato]

The node version set in the pipeline is only used for the specific steps that are controlled (internally) within that pipeline such building or running tests. Heroku is an external environment that uses a different process to pick up on the node version to use. If you asked me, a connection could be made between Bitbucket and heroku to use that very image specified but that would be including an external dependency that would require Bitbucket to change something should Heroku change their process. But that's only my personal opinion