dev

[Hashversion]

• chore(deps): update dependency tailwindcss to ^4.3.0 (chore(deps): update dependency tailwindcss to ^4.3.0 #3)
• chore(deps): update dev dependency minor updates (chore(deps): update dev dependency minor updates #4)
• chore(deps): update node.js to >=22.22.3 (chore(deps): update node.js to >=22.22.3 #5)
• chore(deps): update terraform aws to ~> 6.45.0 (chore(deps): update terraform aws to ~> 6.45.0 #6)
• chore(deps): update terraform hashicorp/terraform to ~> 1.15 (chore(deps): update terraform hashicorp/terraform to ~> 1.15 #8)
• chore(deps): update terraform tls to ~> 4.3 (chore(deps): update terraform tls to ~> 4.3 #9)
• fix(deps): update dependency motion to ^12.38.0 (fix(deps): update dependency motion to ^12.38.0 #10)

Summary by CodeRabbit

• Chores
  • Bumped JavaScript deps: motion, @tailwindcss/postcss, tailwind-merge, tailwind catalog, @types/node, and oxfmt.
  • Raised minimum Node.js requirement to 22.22.3.
  • Upgraded Terraform tooling and provider constraints (AWS, TLS) and updated lockfiles for those providers.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: cd52eff4-1b0c-4eef-a168-d21dc8d25414

📥 Commits

Reviewing files that changed from the base of the PR and between 22a84d8 and b166fbc.

📒 Files selected for processing (2)

• infra/aws/main/main.tf
• infra/aws/static/versions.tf

🚧 Files skipped from review as they are similar to previous changes (1)

• infra/aws/static/versions.tf

---

📝 Walkthrough

Walkthrough

This PR bumps multiple dependency versions: Tailwind catalog and UI plugin, motion and @types/node in the static app, root dev tooling/Node engine, and Terraform required_version plus AWS/TLS provider constraints and lockfiles.

Changes

Dependency Version Updates

Layer / File(s)	Summary
Tailwind and styling dependencies pnpm-workspace.yaml, packages/ui/package.json	Workspace catalog Tailwind updated to ^4.3.0; @tailwindcss/postcss -> ^4.3.0 and tailwind-merge -> ^3.6.0.
Static application dependencies apps/static/package.json	motion bumped ^12.23.27 → ^12.38.0; @types/node devDependency ^22.15.3 → ^22.19.19.
Root development environment package.json	oxfmt devDependency ^0.48.0 → ^0.49.0; engines.node tightened from >=22 to >=22.22.3.
Terraform main infrastructure provider versions infra/aws/main/main.tf, infra/aws/main/.terraform.lock.hcl	required_version raised to ~> 1.15.2; hashicorp/aws ~> 6.45.0 and hashicorp/tls ~> 4.3 with lockfile hashes regenerated.
Terraform static infrastructure provider versions infra/aws/static/versions.tf, infra/aws/static/.terraform.lock.hcl	required_version raised to ~> 1.15.2; hashicorp/aws ~> 6.45.0 and hashicorp/tls ~> 4.3 with lockfile hashes regenerated.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 I hopped through package.json with care,
Bumped Tailwind, motion, types — a tidy affair.
Terraform providers leapt up a notch,
Oxfmt and Node got tightened, watch!
Dependencies aligned, the repo's aware.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'dev' is vague and generic, providing no meaningful information about the changeset which involves multiple dependency updates across the project.	Consider using a more descriptive title such as 'chore: update dependencies' or 'chore: bump tailwindcss, terraform, and other dependencies' to clearly convey the nature of the changes.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dev

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@infra/aws/main/main.tf`:
- Line 2: The Terraform required_version constraint in the config (the line
required_version = "~> 1.15") is newer than the pipeline's Terraform (1.14.3);
update your CI workflow to install/use Terraform 1.15.x (or a compatible 1.15
patch) — e.g., set TF_VERSION to '1.15.0' in the GitHub Actions env or configure
the setup action (hashicorp/setup-terraform) to terraform_version: '~> 1.15' so
pipeline Terraform matches the required_version constraint.

In `@infra/aws/static/versions.tf`:
- Line 2: The pipeline Terraform version must match the module constraint
required_version = "~> 1.15"; update the static infra GitHub Actions workflow to
use Terraform 1.15.x (set TF_VERSION to 1.15.0 or later) or change the setup
step (hashicorp/setup-terraform@v3) to terraform_version: '~> 1.15' so the
runner uses a 1.15.x binary and Terraform init no longer fails.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ed165095-c7b8-4401-a095-5264c6039c01

📥 Commits

Reviewing files that changed from the base of the PR and between 8e19b60 and 22a84d8.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (8)

• apps/static/package.json
• infra/aws/main/.terraform.lock.hcl
• infra/aws/main/main.tf
• infra/aws/static/.terraform.lock.hcl
• infra/aws/static/versions.tf
• package.json
• packages/ui/package.json
• pnpm-workspace.yaml

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | 🏗️ Heavy lift

Pipeline Terraform version must be updated to match required_version constraint.

The pipeline is using Terraform 1.14.3, but this configuration now requires ~> 1.15 (meaning >= 1.15.0 and < 1.16.0). This is causing init failures and blocking all infrastructure deployments.

🔧 Required pipeline configuration update

Update the GitHub Actions workflow file(s) to use Terraform 1.15.x or later:

env:
  TF_VERSION: '1.15.0'  # or latest 1.15.x patch version

Or if using a setup action:

- uses: hashicorp/setup-terraform@v3
  with:
    terraform_version: '~> 1.15'

🧰 Tools

🪛 GitHub Actions: Terraform - Main Infrastructure / 1_Terraform Plan - Main.txt

[error] 2-2: Terraform init failed: Unsupported Terraform Core version. required_version = "~> 1.15" does not support TF_VERSION 1.14.3.

🪛 GitHub Actions: Terraform - Main Infrastructure / Terraform Plan - Main

[error] 2-2: Terraform init failed: Unsupported Terraform Core version. Required 'required_version = "~> 1.15"' but pipeline used TF_VERSION 1.14.3.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@infra/aws/main/main.tf` at line 2, The Terraform required_version constraint
in the config (the line required_version = "~> 1.15") is newer than the
pipeline's Terraform (1.14.3); update your CI workflow to install/use Terraform
1.15.x (or a compatible 1.15 patch) — e.g., set TF_VERSION to '1.15.0' in the
GitHub Actions env or configure the setup action (hashicorp/setup-terraform) to
terraform_version: '~> 1.15' so pipeline Terraform matches the required_version
constraint.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | 🏗️ Heavy lift

Pipeline Terraform version must be updated to match required_version constraint.

The static infrastructure pipeline is also using Terraform 1.14.3, but this configuration now requires ~> 1.15. This is causing the same init failure as the main infrastructure stack.

🔧 Required pipeline configuration update

Update the GitHub Actions workflow file for the static infrastructure to use Terraform 1.15.x or later:

env:
  TF_VERSION: '1.15.0'  # or latest 1.15.x patch version

Or if using a setup action:

- uses: hashicorp/setup-terraform@v3
  with:
    terraform_version: '~> 1.15'

🧰 Tools

🪛 GitHub Actions: Terraform - AWS Static App Infrastructure / 1_Terraform Plan - Main.txt

[error] 2-2: Terraform init failed due to Unsupported Terraform Core version. versions.tf requires required_version = "~> 1.15" but TF_VERSION is 1.14.3.

🪛 GitHub Actions: Terraform - AWS Static App Infrastructure / Terraform Plan - Main

[error] 2-2: Terraform init failed: Unsupported Terraform Core version. versions.tf specifies required_version = "~> 1.15" but pipeline is using TF_VERSION 1.14.3.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@infra/aws/static/versions.tf` at line 2, The pipeline Terraform version must
match the module constraint required_version = "~> 1.15"; update the static
infra GitHub Actions workflow to use Terraform 1.15.x (set TF_VERSION to 1.15.0
or later) or change the setup step (hashicorp/setup-terraform@v3) to
terraform_version: '~> 1.15' so the runner uses a 1.15.x binary and Terraform
init no longer fails.