Skip to content

Adds new integration [jensenbox/ha-arctic-spa]#8841

Open
jensenbox wants to merge 1 commit into
hacs:masterfrom
jensenbox:add-jensenbox-ha-arctic-spa
Open

Adds new integration [jensenbox/ha-arctic-spa]#8841
jensenbox wants to merge 1 commit into
hacs:masterfrom
jensenbox:add-jensenbox-ha-arctic-spa

Conversation

@jensenbox

Copy link
Copy Markdown

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/jensenbox/ha-arctic-spa/releases/tag/v0.1.3
Link to successful HACS action (without the ignore key): https://github.com/jensenbox/ha-arctic-spa/actions/runs/28411570837/job/84185418938
Link to successful hassfest action (if integration): https://github.com/jensenbox/ha-arctic-spa/actions/runs/28411570837/job/84185418964

@hacs-bot hacs-bot Bot changed the title Add jensenbox/ha-arctic-spa Adds new integration [jensenbox/ha-arctic-spa] Jun 30, 2026
@hacs-bot

hacs-bot Bot commented Jun 30, 2026

Copy link
Copy Markdown

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

jensenbox added a commit to jensenbox/ha-arctic-spa that referenced this pull request Jun 30, 2026
…badge, version (#40)

1. .github/release-drafter.yml: add a 'Dependencies' category (label
   'dependencies', collapse-after 3) and map 'dependencies' -> patch.
2. README.md: HACS-Custom badge -> HACS-Default (accurate once
   hacs/default#8841 merges; submitted + all checks green).
3. .pre-commit-config.yaml: add astral-sh/uv-pre-commit 'uv-lock' (keeps
   uv.lock in sync with pyproject.toml) + pre-commit-hooks basics
   (trailing-whitespace, end-of-file-fixer, check-yaml/json/toml,
   check-merge-conflict, check-added-large-files). Runs under the existing
   prek action; ruff stays the Python linter/formatter. Excludes .idea/.
4. pyproject.toml: version 1.0.0 -> 0.1.3 (re-locked uv.lock to match).

Verified: prek run --all-files all pass; 34 tests pass.
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.

1 participant