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.

Sign up for GitHub

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

Jump to bottom

feat: release fix for #805 #831

Merged
merged 1 commit into from
Jun 3, 2022
Merged

feat: release fix for #805 #831

merged 1 commit into from
Jun 3, 2022

Conversation

amuramoto
Copy link
Member

Just kicking off a release because I didn't fix the commit message in #806

Thank you for opening a Pull Request!

Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

  • Make sure to open a GitHub issue as a bug/feature request before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
  • Ensure the tests and linter pass
  • Code coverage does not decrease (if any source code was changed)
  • Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

@amuramoto amuramoto merged commit fede06b into googlemaps:main Jun 3, 2022
googlemaps-bot pushed a commit that referenced this pull request Jun 3, 2022
@semantic-release-bot
chore(release): 2.1.0 [skip ci]
916c5f5 
# [2.1.0](v2.0.1...v2.1.0) (2022-06-03)

### Features

* release fix for [#805](#805) ([#831](#831)) ([fede06b](fede06b))
@googlemaps-bot
Copy link
Contributor

🎉 This PR is included in version 2.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

@arriolac arriolac

Labels
released
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@amuramoto @googlemaps-bot @arriolac