You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This change treats the presence of a `Procfile` as the "source of truth" for how processes should be registered and will skip the default process registration that was previously performed for `npm`, `yarn`, and `pnpm`.
Fixes#908
Related to heroku/buildpacks-go#319
Consider an app with an
index.js
and aProcfile
with contents like:When running a build with
heroku/builder:24
, this results an image with two processes:This is probably unexpected for the user. There is an extra process, and the extra
web
process is unlikely to accept http connections anyway.My feeling is that we should probably avoid adding processes if we know the the procfile buildpack was detected and is part of the build plan.
The text was updated successfully, but these errors were encountered: