Bump aioimmich to 0.14.1

[mib1185]

Proposed change

release-notes: https://github.com/mib1185/aioimmich/releases/tag/v0.14.1
diff: mib1185/aioimmich@v0.14.0...v0.14.1
important change:

• Fix get all albums from cached results mib1185/aioimmich#52

This fixes a bug when fetching all albums multiple times from a cached response in the lib.

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 Shared album replicated in media view whenever opened again #169866
• This PR is related to issue:
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• 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.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

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

• Documentation added/updated for www.home-assistant.io

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 diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[Copilot]

Pull request overview

This pull request updates the Immich integration’s pinned aioimmich dependency to version 0.14.1 to pick up an upstream bugfix (noted as fixing #169866).

Changes:

• Bump aioimmich from 0.14.0 to 0.14.1 in the Immich integration manifest.
• Update the pinned version in requirements_all.txt and requirements_test_all.txt to keep dependency lockfiles consistent.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
homeassistant/components/immich/manifest.json	Updates the integration requirement pin to aioimmich==0.14.1.
requirements_all.txt	Updates the global pinned dependency list for runtime installs.
requirements_test_all.txt	Updates the pinned dependency list used for the full test environment.

[github-actions]

⚠️ Some checks require attention — see the details below.

Requirements Check

Package	Type	Old→New	License	Repo Public	CI Upload	Release Pipeline	PR Link	Diff Consistent
aioimmich	bump	0.14.0→0.14.1	✅	✅	❌	❌	✅	✅

aioimmich 📦 bump 0.14.0→0.14.1

• License: ✅ Apache-2.0 — in the approved SPDX list.
• Repository Public: ✅ https://github.com/mib1185/aioimmich is publicly accessible.
• CI Upload: ❌ No provenance attestation found for aioimmich-0.14.1-py3-none-any.whl (PyPI returned 404 for the integrity endpoint). The release was likely uploaded without a Trusted Publisher / OIDC attestation.
• Release Pipeline: ❌ The release workflow publishes to PyPI using a static long-lived API token (secrets.PYPI_TOKEN passed as password: to pypa/gh-action-pypi-publish). There is no id-token: write permission and no OIDC Trusted Publisher configured. Please migrate to PyPI Trusted Publishing so that future releases get provenance attestations and no long-lived token is required.
  • Additionally, the publish job is triggered by any push to main (not just tag pushes or release: published), which means every merge to main attempts a PyPI publish.
• PR Link: ✅ mib1185/aioimmich@v0.14.0...v0.14.1 correctly references both old and new versions.
• Diff Consistent: ✅ 0.14.0 → 0.14.1 is a forward version bump.

Generated by Requirements License and Availability Check for issue #171138 · ● 292.5K · ◷

[erwindouna]

Thanks @mib1185!