Skip to content

Conversation

ludeeus
Copy link
Member

@ludeeus ludeeus commented Aug 6, 2025

Proposed change

I do not use this anymore, and no longer wishes to be responsible for managing it.

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

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:
  • Link to developer documentation pull request:
  • Link to frontend pull request:

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 Ruff (ruff format 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.

To help with the load of incoming pull requests:

Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR removes the contributor as a code owner from the traccar_server integration, as they no longer use the integration and wish to step down from maintaining it. The change updates both the manifest.json file and the CODEOWNERS file to reflect this ownership change.

  • Remove codeowner entry from traccar_server integration manifest
  • Remove traccar_server paths from the CODEOWNERS file

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
homeassistant/components/traccar_server/manifest.json Clears the codeowners array to remove the maintainer
CODEOWNERS Removes the traccar_server component and test paths from the codeowners list

Copy link
Member

@joostlek joostlek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the love you put into it ❤️

@joostlek joostlek merged commit 33421bd into dev Aug 6, 2025
34 checks passed
@joostlek joostlek deleted the remove-myself branch August 6, 2025 12:51
@ludeeus
Copy link
Member Author

ludeeus commented Aug 6, 2025

Thanks for merging @joostlek 🙏

@github-actions github-actions bot locked and limited conversation to collaborators Aug 7, 2025
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.

2 participants