Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Input 'app-id' has been deprecated with message: Use 'client-id' instead.

Too many nested callbacks (5). Maximum allowed is 4

Too many nested callbacks (5). Maximum allowed is 4

Too many nested callbacks (5). Maximum allowed is 4

Too many nested callbacks (5). Maximum allowed is 4

Too many nested callbacks (5). Maximum allowed is 4

Unexpected any. Specify a different type

Input 'app-id' has been deprecated with message: Use 'client-id' instead.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, googleapis/release-please-action@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Input 'app-id' has been deprecated with message: Use 'client-id' instead.

Input 'app-id' has been deprecated with message: Use 'client-id' instead.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Input 'app-id' has been deprecated with message: Use 'client-id' instead.

Input 'app-id' has been deprecated with message: Use 'client-id' instead.

Using package manager: npm

Using package manager: npm

Using package manager: npm

Release PR exists (branch: release-please--branches--main--components--heroku-cli-util)

✓ Manifest file verified: .github/release-configs/release-please-manifest.json

✓ Config file verified: .github/release-configs/release-please-config.json

npm distribution tag: latest

Using manifest file: .github/release-configs/release-please-manifest.json

Selected channel config: .github/release-configs/release-please-config.json

Detected branch: main

Using package manager: npm

Using package manager: npm

Using package manager: npm

Using package manager: npm

PR branch found: release-please--branches--main--components--heroku-cli-util