8000 Replace foscam dependency by Foscam-wangzhengyu · Pull Request #145766 · home-assistant/core · GitHub
[go: up one dir, main page]

Skip to content

Replace foscam dependency #145766

< 8000 div class="gh-header-actions mt-0 mb-3 mb-md-2 ml-1 flex-md-order-1 flex-shrink-0 d-flex flex-items-center gap-1">
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

Open
wants to merge 4 commits into
base: dev
Choose a base branch
from

Conversation

Foscam-wangzhengyu
Copy link
@Foscam-wangzhengyu Foscam-wangzhengyu commented May 28, 2025

Breaking change

Proposed change

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:

@home-assistant home-assistant bot added cla-signed integration: foscam small-pr PRs with less than 30 lines. labels May 28, 2025
@home-assistant
Copy link

Hey there @krmarien, mind taking a look at this pull request as it has been labeled with an integration (foscam) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of foscam can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign foscam Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

@Foscam-wangzhengyu
Copy link
Author

@joostlek I’m one of the developers from FOSCAM. We had a brief communication last month regarding the integration library.
After waiting for nearly a month, I have not received any response from the original author of the current library. In order to ensure more efficient maintenance and development moving forward, I would like to formally request approval to replace the existing library.

@epenet epenet changed the title Update Public Library Replace foscam dependency May 28, 2025
@epenet
Copy link
Contributor
epenet commented May 28, 2025

@joostlek I’m one of the developers from FOSCAM. We had a brief communication last month regarding the integration library. After waiting for nearly a month, I have not received any response from the original author of the current library. In order to ensure more efficient maintenance and development moving forward, I would like to formally request approval to replace the existing library.

Please update the PR description, and fill in details:

  • link to the new dependency repository
  • link to the change log and/or release notes
  • link to the attempts contacting the code-owner
  • ...

@Foscam-wangzhengyu
Copy link
Author

1.new dependency repository
https://github.com/Foscam-wangzhengyu/libfoscamcgi
2.release notes
https://github.com/Foscam-wangzhengyu/libfoscamcgi/edit/main/README.md
3.attempts contacting the code-owner

image

@Foscam-wangzhengyu
Copy link
Author

@epenet Understood, these are some of my information. I don't have much experience in developing open source projects. If there are any errors in the information, I will cooperate and make necessary modifications in a timely manner

@joostlek
Copy link
Member

So the requirements for new dependencies are here https://developers.home-assistant.io/docs/core/integration-quality-scale/rules/dependency-transparency. I think the only thing that is missing is that the releases should be tagged

@Foscam-wangzhengyu
Copy link
Author

@joostlek
Regarding Home Assistant's requirements for dependency libraries:

1.The source code of the dependency must be available under an OSI-approved license.

I have already licensed my project under the GPL-3.0 License.

2.The dependency must be available on PyPI.

I have uploaded my dependency library to PyPI.

3.Packages published to PyPI should be built and released through a public CI pipeline.

I uploaded the dependency using a public CI workflow.

4.The versions of the dependency published on PyPI should correspond to the tagged versions in the publicly accessible online repository.

The versions are consistent.

I'm not sure if I’ve missed any steps — would you please let me know if anything needs correction? I’ll update it promptly. Thank you

@epenet
Copy link
Contributor
epenet commented May 28, 2025

4.The versions of the dependency published on PyPI should correspond to the tagged versions in the publicly accessible online repository.

These are empty:

@Foscam-wangzhengyu
Copy link
Author

@epenet Thank you for the reminder, I did miss that step

@Foscam-wangzhengyu
Copy link
Author

@epenet I believe I have completed the steps you just mentioned.

@epenet
Copy link
Contributor
epenet commented May 28, 2025

There is no need to do Merge branch 'dev' into foscam

Also, please run the test suite locally with pytest tests\components\foscam to ensure all tests are working as expected

==================================== ERRORS ====================================
___________________ ERROR collecting tests/components/foscam ___________________
tests/components/foscam/conftest.py:3: in <module>
    from libpyfoscam.foscam import (
E   ModuleNotFoundError: No module named 'libpyfoscam'
=========================== short test summary info ============================
ERROR tests/components/foscam - ModuleNotFoundError: No module named 'libpyfoscam'
!!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!!

@Foscam-wangzhengyu
Copy link
Author

@epenet The test files have been updated according to your requirements and are now running successfully locally. Thank you again for your patient guidance!

@Foscam-wangzhengyu
Copy link
Author

@joostlek Hello, I'm sorry to bother you. I'd like to kindly ask when my PR might be merged.

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.

3 participants
0