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

Bump gcal_sync to 6.0.1 #103861

Merged
merged 1 commit into from Nov 12, 2023
Merged

Bump gcal_sync to 6.0.1 #103861

merged 1 commit into from Nov 12, 2023

Conversation

allenporter
Copy link
Contributor

Proposed change

Bump gcal_sync to 6.0.1

Release notes: https://github.com/allenporter/gcal_sync/releases/tag/6.0.1
Files changed: allenporter/gcal_sync@5.0.0...6.0.1

The motivation is to pull in client side fixes to gracefully handle invalid Google Calendars RRULES #91119 there there is an additional bug in home assistant that also needs to be fixed in a followup PR. The release also contains another change to not leak pydantic exceptions (not caught today in home assistant), wrapping them with a calendar api exception.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Black (black --fast homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
  • Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

@MartinHjelmare MartinHjelmare merged commit fd7d2df into home-assistant:dev Nov 12, 2023
52 of 53 checks passed
@allenporter allenporter added this to the 2023.11.3 milestone Nov 12, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Nov 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants