Add a warning when multiple package managers are found#1692
Merged
Conversation
Currently the buildpack will use whichever package manager it finds first, if the files of multiple package managers are found. This occasionally results in support tickets where the user believes the build to not be installing dependencies correctly, when in fact they are adding dependencies to the wrong package manager file. As such, we want to make the presence of multiple package manager files an error, but first we should add a warning so it's not a surprise. (Plus with the recent Poetry support addition, there will be apps using the third party Poetry buildpack that have both a `poetry.lock` and the generated `requirements.txt` until they remove the third-party buildpack.) Towards #1691. GUS-W-17167927.
edmorley
force-pushed
the
multiple-package-manager-warning
branch
from
0872bcd to
ce7296c
Compare
colincasey
approved these changes
Nov 8, 2024
colincasey
left a comment
colincasey
left a comment
There was a problem hiding this comment.
Learning from my mistake by making the detection of multiple package managers a warning before making it an error 😅
Merged
edmorley
added a commit
that referenced
this pull request
Dec 9, 2025
Currently the buildpack will use whichever package manager it finds first, if the files of multiple package managers are found. This occasionally results in support tickets where the user believes the build to not be installing dependencies correctly, when in fact they are adding dependencies to the wrong package manager file. It also means historic users of third-party Poetry and uv buildpacks might not realise that the buildpack now natively supports those package managers (in a much more efficient way), if they missed our release announcements. As such, in November 2024 in #1692 a warning was added, which we're now converting to an error. Users with multiple package manager files committed to their Git repo will need to pick one package manager and delete the files relating to the others. And users who are still using the third-party Poetry or uv buildpacks will need to remove those buildpacks from their app: https://devcenter.heroku.com/articles/managing-buildpacks#remove-classic-buildpacks GUS-W-18915632.
edmorley
added a commit
that referenced
this pull request
Dec 9, 2025
Currently the buildpack will use whichever package manager it finds first, if the files of multiple package managers are found. This occasionally results in support tickets where the user believes the build to not be installing dependencies correctly, when in fact they are adding dependencies to the wrong package manager file. It also means historic users of third-party Poetry and uv buildpacks might not realise that the buildpack now natively supports those package managers (in a much more efficient way), if they missed our release announcements. As such, in November 2024 in #1692 a warning was added, which we're now converting to an error. Users with multiple package manager files committed to their Git repo will need to pick one package manager and delete the files relating to the others. And users who are still using the third-party Poetry or uv buildpacks will need to remove those buildpacks from their app: https://devcenter.heroku.com/articles/managing-buildpacks#remove-classic-buildpacks Closes #1691. GUS-W-18915632.
edmorley
added a commit
that referenced
this pull request
Dec 10, 2025
Currently the buildpack will use whichever package manager it finds first, if the files of multiple package managers are found. This occasionally results in support tickets where the user believes the build to not be installing dependencies correctly, when in fact they are adding dependencies to the wrong package manager file. It also means historic users of third-party Poetry and uv buildpacks might not realise that the buildpack now natively supports those package managers (in a much more efficient way), if they missed our release announcements. As such, in November 2024 in #1692 a warning was added, which we're now converting to an error. Users with multiple package manager files committed to their Git repo will need to pick one package manager and delete the files relating to the others. And users who are still using the third-party Poetry or uv buildpacks will need to remove those buildpacks from their app: https://devcenter.heroku.com/articles/managing-buildpacks#remove-classic-buildpacks Closes #1691. GUS-W-18915632.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently the buildpack will use whichever package manager it finds first, if the files of multiple package managers are found.
This occasionally results in support tickets where the user believes the build to not be installing dependencies correctly, when in fact they are adding dependencies to the wrong package manager file.
As such, we want to make the presence of multiple package manager files an error, but we're first adding a warning so it's not a surprise. (Plus with the recent Poetry support addition, there will be apps using the third party Poetry buildpack that have both a
poetry.lockand the generatedrequirements.txtuntil they remove the third-party buildpack.)Towards #1691.
GUS-W-17167927.