Error: Command failed: git push heroku HEAD:refs/heads/main --force remote: Updated 40 paths from 0f53461 remote: Compressing source files... done. remote: Building source: remote: remote: -----> Building on the Heroku-22 stack remote: -----> Using buildpack: heroku/nodejs remote: -----> Node.js app detected remote: remote: -----> Creating runtime environment remote: remote: NPM_CONFIG_LOGLEVEL=error remote: USE_YARN_CACHE=true remote: NODE_OPTIONS=--max_old_space_size=2560 remote: NODE_VERBOSE=false remote: NODE_ENV=production remote: NODE_MODULES_CACHE=true remote: remote: -----> Installing binaries remote: engines.node (package.json): >=16 <=19 remote: engines.npm (package.json): unspecified (use default) remote: engines.yarn (package.json): unspecified (use default) remote: remote: Resolving node version >=16 <=19... remote: Downloading and installing node 18.18.2... remote: Using default npm version: 9.8.1 remote: Resolving yarn version 1.22.x... remote: Downloading and installing yarn (1.22.19) remote: Installed yarn 1.22.19 remote: remote: -----> Restoring cache remote: Cached directories were not restored due to a change in version of node, npm, yarn or stack remote: Module installation may take longer for this build remote: remote: -----> Installing dependencies remote: Installing node modules (yarn.lock) remote: yarn install v1.22.19 remote: [1/4] Resolving packages... remote: [2/4] Fetching packages... remote: [3/4] Linking dependencies... remote: warning " > @octokit/[email protected]" has unmet peer dependency "@octokit/core@^4.0.0". remote: [4/4] Building fresh packages... remote: info This package requires node-gyp, which is not currently installed. Yarn will attempt to automatically install it. If this fails, you can run "yarn global add node-gyp" to manually install it. remote: [1/4] Resolving packages... remote: error /tmp/build_46608c1b/node_modules/zlib-sync: Failed to auto-install node-gyp. Please run "yarn global add node-gyp" manually. Error: "Couldn't find any versions for \"node-gyp\" that matches \"latest\" in our cache (possible versions are \"\"). This is usually caused by a missing entry in the lockfile, running Yarn without the --offline flag may help fix this issue." remote: info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. remote: remote: -----> Build failed remote: remote: We're sorry this build is failing! You can troubleshoot common issues here: remote: https://devcenter.heroku.com/articles/troubleshooting-node-deploys remote: remote: Some possible problems: remote: remote: - Dangerous semver range (>) in engines.node remote: https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version remote: remote: Love, remote: Heroku remote: remote: ! Push rejected, failed to compile Node.js app. remote: remote: ! Push failed remote: ! remote: ! ## Warning - The same version of this code has already been built: a5c8403113ee02868a71b856875b295e87dd1500 remote: ! remote: ! We have detected that you have triggered a build from source code with version a5c8403113ee02868a71b856875b295e87dd1500 remote: ! at least twice. One common cause of this behavior is attempting to deploy code from a differ