From bd55e49e36b46eda63c44cfba87bb18d0cf3cf0d Mon Sep 17 00:00:00 2001
From: Tom Keller <1083460+kellertk@users.noreply.github.com>
Date: Thu, 14 May 2026 14:38:34 -0700
Subject: [PATCH] chore: lint fix (whitespace)

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index fc7a07e..df38357 100644
--- a/README.md
+++ b/README.md
@@ -574,7 +574,7 @@ To align with the Amazon IAM best practice of [granting least
 privilege][least-privilege], the assume role policy document should contain a
 [`Condition`](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html)
 that restricts which workflows can assume the role. Without any condition, any
-GitHub user or repository could potentially assume the role. 
+GitHub user or repository could potentially assume the role.
 
 GitHub provides a number of additional claims in the OIDC token that you can use
 in your IAM policies to scope down permissions. Early versions of this action