Skip to content

Rename S3 integration also in the release blog #38908

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

Merged
merged 1 commit into from
May 6, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions source/_posts/2025-05-07-release-20255.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -281,9 +281,8 @@ We welcome the following new integrations in this release:
- **[ntfy]**, added by [@tr4nt0r]
Integrates with [ntfy.sh], a simple HTTP-based pub-sub notification service
that allows you to send notifications to your phones or desktops.
- **[S3]**, added by [@tomasbedrich]
Use an [Amazon S3 storage] bucket–or any S3 API compatible storage provider–
as a backup location for your Home Assistant backups.
- **[AWS S3]**, added by [@tomasbedrich]
Use an [Amazon S3 storage] bucket as a backup location for your Home Assistant backups.

To process:
- Add Rehlko (formerly Kohler Energy Management) Integration ([@PeteRager] - [#143602])
Expand All @@ -300,7 +299,7 @@ To process:
[Miele]: /integrations/miele
[ntfy.sh]: https://ntfy.sh/
[ntfy]: /integrations/ntfy
[S3]: /integrations/s3
[AWS S3]: /integrations/aws_s3
Copy link
Contributor

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

Verify that the AWS S3 integration docs exist at the new path
Please confirm that /integrations/aws_s3 is the correct slug and that the corresponding documentation file is present.

Run the following script to verify the existence of the integration doc:


🏁 Script executed:

#!/bin/bash
# Description: Check for AWS S3 integration documentation under docs/integrations
fd aws_s3 docs/integrations

Length of output: 134


🏁 Script executed:

#!/bin/bash
# Locate any 'integrations' directories
fd -t d integrations

# Find files or directories matching 'aws_s3*'
fd aws_s3*

# Search throughout the repo for references to 'aws_s3'
rg -n 'aws_s3' .

Length of output: 432


🏁 Script executed:

#!/bin/bash
# Search for AWS S3 integration docs under source/integrations and source/_integrations
echo "Files under source/integrations matching 'aws' or 's3':"
fd -t f -i 'aws' source/integrations || true
fd -t f -i 's3' source/integrations || true

echo
echo "Files under source/_integrations matching 'aws' or 's3':"
fd -t f -i 'aws' source/_integrations || true
fd -t f -i 's3' source/_integrations || true

echo
echo "Ripgrep for 'S3' in both directories:"
rg -n 'S3' source/integrations source/_integrations || true

Length of output: 4356


Correct AWS S3 integration link
The current slug /integrations/aws_s3 does not map to any docs. The S3 integration lives in source/_integrations/s3.markdown, which generates the /integrations/s3 slug. Please update line 302 in source/_posts/2025-05-07-release-20255.markdown:

-[AWS S3]: /integrations/aws_s3
+[AWS S3]: /integrations/s3
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
[AWS S3]: /integrations/aws_s3
[AWS S3]: /integrations/s3


This release also has new virtual integrations. Virtual integrations
are stubs that are handled by other (existing) integrations to help with
Expand Down