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

Hotfix freeze gmaps version #13562

Merged
merged 10 commits into from
Feb 28, 2018
Merged

Hotfix freeze gmaps version #13562

merged 10 commits into from
Feb 28, 2018

Conversation

ivanmalagon
Copy link
Contributor

A recent deploy of a new GMaps experimental version (v3.32) behaves differently and breaks some behaviour in carto.js.

Builder is mostly safe because when requesting a previous version, it serves the stable one. Even if you ask for 3.12. it'll serve the 3.30. We only have a potential problem in static.js where we don't explicitly ask for one, so the most experimental one is served.

This PR:

  • Updates cartodb.jsto the fixed versions, both v3 and v4.
  • Sets every reference to GMaps script to the currently frozen version, v3.30. This is the version where we know it has worked for the last year at least.

Possible enhancements

  • Set GMaps version in app_config.yml and use it throughout all .rb files. I didn't feel confident at all to do that change to the backend code. Feel free to jump in and do it.

@javitonino
Copy link
Contributor

Ready for acceptance ✨

@ivanmalagon
Copy link
Contributor Author

Accepted.

@ivanmalagon ivanmalagon merged commit f66d025 into master Feb 28, 2018
@ivanmalagon ivanmalagon deleted the hotfix-freeze-gmaps-version branch February 28, 2018 16:04
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.

2 participants