This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Log in to ask a question

Looker 25.8 Release Notes

Posted Tuesday
sam8
Staff
Reply posted on --/--/---- --:-- AM

Looker 25.8 is launching this month! 

📆 Release dates: 

  • Expected Looker (original) deployment start: Monday, May 19, 2025

  • Expected Looker (original) final deployment and download available: Thursday, May 29, 2025

  • Expected Looker (Google Cloud core) deployment start: Monday, May 19, 2025

  • Expected Looker (Google Cloud core) final deployment: Monday, June 2, 2025

⚡️ Breaking changes: 

  • An issue has been fixed where HTML in a LookML dimension wasn't being applied to Y-axis labels. HTML formatting will now be applied to Y-axis labels, potentially changing existing visualizations.

  • SSL host validation is now enabled by default. If any of your SSL certificates are invalid, certain Looker workflows may break.

⭐️ Notable features: 

  • The Code Interpreter in Conversational Analytics is now available in Preview. The Code Interpreter translates your natural language questions into Python code and executes that code to provide advanced analysis and visualizations. The Code Interpreter is disabled by default. Admins of Looker (original) instances can manage enablement for the Code Interpreter on the Gemini in Looker admin page.

  • You can now create connections using the Amazon Redshift 2.1+ or Amazon Redshift Serverless 2.1+ SQL dialect, both of which use the Redshift JDBC driver. Connections with the original Amazon Redshift SQL dialect option use the Postgres JDBC driver.

  • The Presto JDBC driver version has been updated to 0.291.

  • You can now select the JDBC driver version when you create or edit a connection.

  • The sync_lookml_dashboard API endpoint now accepts an optional dashboard_ids parameter to specify a subset of dashboards to synchronize.

  • The gemini_in_looker permission can now be applied to selected models on the Looker instance. The Gemini role still applies the gemini_in_looker permission to all models on the Looker instance; however, if needed, Looker admins can manually restrict use of Gemini in Looker to specific models by creating and assigning a Looker role with gemini_in_looker permissions on limited models.

Check the release notes for more details. Happy Lookering!

0 0 66
Topic Labels
0 Likes
0 REPLIES 0