Adds new integration [dext0r/ha-yandex-station-intents]

[dext0r]

Checklist

• I've read the publishing documentation.
• I've added the HACS action to my repository.
• (For integrations only) I've added the hassfest action to my repository.
• The actions are passing without any disabled checks in my repository.
• I've added a link to the action run on my repository below in the links section.
• I've created a new release of the repository after the validation actions were run successfully.

Links

Link to current release: https://github.com/dext0r/ha-yandex-station-intents/releases/tag/v0.6.5
Link to successful HACS action (without the ignore key): https://github.com/dext0r/ha-yandex-station-intents/actions/runs/23686501277/job/69006765394
Link to successful hassfest action (if integration): https://github.com/dext0r/ha-yandex-station-intents/actions/runs/23686501277/job/69006765394

[hacs-bot]

Thank you for submitting your repository to HACS (Home Assistant Community Store).

Your submission is in the review queue:
Your repository is waiting to be reviewed and included in HACS.

You can view the current queue here. Pull requests are processed in the order they were created, oldest first.

What to avoid during review:
To help reviewers work efficiently, don't do the following:

• Comment on the pull request - The reviewer will contact you when they have feedback or questions.
• Open a new pull request - This won't speed up the process and creates duplicate work.
• Ask followers to comment on the pull request - This won't speed up the process and may delay your review.
• Merge in the default branch - Only do this if a maintainer asks you to resolve a merge conflict.

If you need to make changes:
You can continue updating your repository while waiting for review. Changes to your repository will be reflected when the reviewer examines it. Only comment on the pull request if you need to withdraw your submission or have critical information for reviewers.

About draft pull requests:
Draft pull requests aren't included in the review queue. Your pull request may be marked as draft by a reviewer if issues need to be addressed. Once you've resolved all issues, mark it as ready for review to re-enter the queue.

What happens next:
Once a reviewer examines your submission, they'll either:

• Approve and merge your pull request if everything meets the requirements
• Request changes or ask questions if adjustments are needed

[frenck]

Hi @dext0r,

This PR has merge conflicts with master and needs a rebase before it can be reviewed and merged. Please pull the latest hacs:master into your branch (or rebase on it), resolve the conflict in the integration file, and push the updated branch. CI will re-run and I'll pick it up from there.

../Frenck

                       

Blogging my personal ramblings at frenck.dev

[frenck]

Hi @dext0r, thanks for the submission! 👋

This needs a LICENSE file (or LICENSE.md) at the repository root before it can be added to the HACS default catalog. That's a required item per the publishing docs (https://hacs.xyz/docs/publish/start). Without one, users have no granted rights to redistribute or modify the integration.

Please pick a license (MIT, Apache 2.0, GPL, etc.), commit the LICENSE file to the repo root, cut a new release that includes it, and re-request review (or open a fresh PR if this one ends up closed in the meantime).

../Frenck

                       

Blogging my personal ramblings at frenck.dev

[dext0r]

Hi @dext0r, thanks for the submission! 👋

This needs a LICENSE file (or LICENSE.md) at the repository root before it can be added to the HACS default catalog. That's a required item per the publishing docs (https://hacs.xyz/docs/publish/start). Without one, users have no granted rights to redistribute or modify the integration.

Please pick a license (MIT, Apache 2.0, GPL, etc.), commit the LICENSE file to the repo root, cut a new release that includes it, and re-request review (or open a fresh PR if this one ends up closed in the meantime).

../Frenck

                       

Blogging my personal ramblings at frenck.dev

Hello. MIT license was added in the new release.

This needs a LICENSE file (or LICENSE.md) at the repository root before it can be added to the HACS default catalog. That's a required item per the publishing docs (https://hacs.xyz/docs/publish/start). Without one, users have no granted rights to redistribute or modify the integration.

I don't see any requirements about licensing in the publishing docs.

[hacs-bot]

Your branch seems out of date. Please update your branch with the latest changes from the base branch.