Skip to content

chore(main): release 8.7.0 - #1014

Open
googlemaps-bot wants to merge 1 commit into
mainfrom
release-please--branches--main
Open

googlemaps-bot wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@googlemaps-bot

@googlemaps-bot googlemaps-bot commented Sep 22, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

8.7.0 (2026-09-23)

Features

  • ci: publish an instrumented coverage badge (#1009) (b0d6420)

This PR was generated with Release Please. See documentation.

@github-actions

Copy link
Copy Markdown

Coverage (unit tests)

No unit baseline recorded in coverage/history.csv yet, so this run only reports absolute numbers.

Module Line % Change Branch % Change
maps-compose 0.00% new 0.00% new
maps-compose-utils 2.04% new 0.49% new
maps-compose-widgets 0.00% new 0.00% new
TOTAL 0.42% new 0.09% new

Line and branch coverage from unit test reports. History is recorded in coverage/history.csv after each merge to main.

@googlemaps-bot

Copy link
Copy Markdown
Contributor Author

Code Coverage

Overall Project 24.59% ❌

There is no coverage information present for the Files changed

@googlemaps-bot
googlemaps-bot force-pushed the release-please--branches--main branch from 597a1fd to 72b5da8 Compare September 23, 2026 19:49

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants