Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include origin of versions in build output #50

Merged
merged 1 commit into from
May 16, 2024

Conversation

edmorley
Copy link
Member

@edmorley edmorley commented May 16, 2024

Previously the build output only stated what version of GDAL/GEOS/PROJ was being installed, and not why that version was chosen.

In particular, this made the "the version you requested doesn't exist for this stack" message confusing for the case where the user didn't pick a version, but instead the version was inherited from the previous build via the cache.

Now, the origin of the versions is logged.

In addition, the "version not available for this stack" message has been tweaked to not (falsely) suggest the version was always explicitly requested, plus explain how to adjust the version using the env var or clearing the build cache.

These changes should make stack upgrades less frustrating (such as for the upcoming Heroku-24 release).

Lastly, some best practices have been applied to the curl usage.

GUS-W-15803983.

Previously the build output only stated what version of GDAL/GEOS/PROJ
was being installed, and not why that version was chosen.

In particular, this made the "the version you requested doesn't exist
for this stack" message confusing for the case where the user didn't
pick a version, but instead the version was inherited from the previous
build via the cache.

Now, the origin of the versions is logged.

In addition, the "version not available for this stack" message has been
tweaked to not (falsely) suggest the version was always explicitly
requested, plus explain how to adjust the version using the env var or
clearing the build cache.

These changes should make stack upgrades less frustrating (such as for
the upcoming Heroku-24 release).

Lastly, some best practices have been applied to the curl usage.
@edmorley edmorley self-assigned this May 16, 2024
@edmorley edmorley marked this pull request as ready for review May 16, 2024 09:48
@edmorley edmorley merged commit eac3679 into main May 16, 2024
3 checks passed
@edmorley edmorley deleted the edmorley/build-output-improvements branch May 16, 2024 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant