chore: update deps - #14
Conversation
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
📝 WalkthroughWalkthroughThis PR upgrades Terraform infrastructure tooling from version 1.14.3 to 1.15.2 and bumps associated provider versions, while simultaneously updating JavaScript workspace dependencies including Tailwind CSS, motion, oxfmt, and Node.js engine requirements across multiple packages. ChangesDependency and Version Upgrades
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 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 12: The Terraform TLS provider version constraint currently uses "~> 4.3"
which is not released; update the constraint to the latest stable series by
changing the version string in the provider declaration (the line containing
version = "~> 4.3") to "~> 4.2" so the TLS provider uses the 4.2.x release
series.
In `@package.json`:
- Line 20: package.json bumps the "oxfmt" dependency to "^0.49.0", which
contains a breaking change that makes oxfmt respect more gitignore rules;
confirm this change won't break formatting in your repo by running the formatter
and CI, and either pin to a safe prior version (e.g., change "oxfmt" to the
previous semver) or update repo ignore/config files to accommodate the new
behavior; specifically, run oxfmt against the codebase, check for missing files
now ignored, adjust .gitignore or oxfmt config as needed, update CHANGELOG or PR
notes to call out the behavior change, and add/adjust tests or CI formatting
checks to guard against regressions.
In `@pnpm-workspace.yaml`:
- Line 9: The project is being upgraded to Tailwind CSS 4.3.0 which deprecates
start-* and end-* utilities; search the codebase for any usages of start-* and
end-* (in templates, .css/.scss files, React/Vue/TSX/JSX components and
tailwind.config.js) and replace them with the new inset-s-* and inset-e-*
equivalents, update any custom plugin/shorthand definitions in
tailwind.config.js that emit start/end utilities to emit inset-s/inset-e, and
run the Tailwind build to verify no remaining references and that layout/rtl
behavior remains correct.
🪄 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: ef0a8f0b-d92b-418d-b6fe-0adf1da19291
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (10)
.github/workflows/infra-main.yaml.github/workflows/infra-static.yamlapps/static/package.jsoninfra/aws/main/.terraform.lock.hclinfra/aws/main/main.tfinfra/aws/static/.terraform.lock.hclinfra/aws/static/versions.tfpackage.jsonpackages/ui/package.jsonpnpm-workspace.yaml
| tls = { | ||
| source = "hashicorp/tls" | ||
| version = "~>4.1" | ||
| version = "~> 4.3" |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
HashiCorp TLS provider 4.3 changelog
💡 Result:
As of May 16, 2026, there is no official changelog for a version 4.3 of the HashiCorp TLS provider [1][2][3]. The latest released version of the provider is 4.2.1, which was released on January 30, 2026 [4][5]. While version 4.3.0 is listed in the HashiCorp releases directory [3], it does not currently have an associated release, changelog, or published documentation, indicating it has not been officially released as of this date. Users should rely on the 4.2.x series for the most recent stable features and bug fixes [2][4].
Citations:
- 1: https://github.com/hashicorp/terraform-provider-tls/blob/main/CHANGELOG.md
- 2: https://github.com/hashicorp/terraform-provider-tls/releases
- 3: https://releases.hashicorp.com/terraform-provider-tls/
- 4: https://github.com/hashicorp/terraform-provider-tls/releases/tag/v4.2.1
- 5: https://github.com/hashicorp/terraform-provider-tls
Update TLS provider version to 4.2—version 4.3 has not been released.
Version 4.3.0 does not currently have an official release or published documentation. The latest stable version is 4.2.1 (released January 30, 2026). Change the version constraint from ~> 4.3 to ~> 4.2 to use the most recent stable release.
🤖 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 12, The Terraform TLS provider version
constraint currently uses "~> 4.3" which is not released; update the constraint
to the latest stable series by changing the version string in the provider
declaration (the line containing version = "~> 4.3") to "~> 4.2" so the TLS
provider uses the 4.2.x release series.
| "@commitlint/config-conventional": "^20.5.3", | ||
| "lefthook": "^2.1.6", | ||
| "oxfmt": "^0.48.0", | ||
| "oxfmt": "^0.49.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
oxfmt npm package version 0.49.0
💡 Result:
The oxfmt npm package version 0.49.0 was published on May 11, 2026 [1][2][3]. Oxfmt is a high-performance code formatter designed for the JavaScript ecosystem, built on the Oxc (Oxidation Compiler) stack [4][5]. It is intended for use in large codebases and CI environments, emphasizing high throughput and predictable performance [4][6]. Key details regarding the package include: - Functionality: It supports formatting for various languages and formats, including JavaScript, JSX, TypeScript, TSX, JSON, JSONC, JSON5, YAML, TOML, HTML, Angular, Vue, CSS, SCSS, Less, Markdown, MDX, GraphQL, Ember, and Handlebars [5][7]. - Usage: It can be installed as a development dependency using package managers like npm, pnpm, yarn, or bun [8][4]. - Ecosystem: The package utilizes various platform-specific bindings (e.g., @oxfmt/binding-linux-arm-musleabihf, @oxfmt/binding-win32-arm64-msvc) to support its high-performance requirements across different environments [2][3][9].
Citations:
- 1: https://npmx.dev/package/oxfmt/versions
- 2: https://www.npmjs.com/package/@oxfmt/binding-linux-arm-musleabihf
- 3: https://www.npmjs.com/package/@oxfmt/binding-win32-arm64-msvc?activeTab=readme
- 4: https://oxc.rs/docs/guide/usage/formatter.html
- 5: https://dev.to/ramunarasinga-11/oxfmt-a-high-performance-formatter-for-the-javascript-ecosystem-1mfj
- 6: https://oxc.npmjs.net.cn/docs/guide/usage/formatter
- 7: https://medium.com/@ramunarasinga/oxfmt-a-high-performance-formatter-for-the-javascript-ecosystem-a6fcc5737cf3
- 8: https://oxc.rs/docs/guide/usage/formatter/quickstart
- 9: https://www.npmjs.com/package/@oxfmt/binding-darwin-x64
🌐 Web query:
oxfmt 0.49.0 changelog release notes breaking changes
💡 Result:
Oxfmt version 0.49.0 was released as part of the Oxc project updates [1]. Breaking Changes: - The primary breaking change in version 0.49.0 is that oxfmt now respects more git ignore options, aligning its behavior with oxlint [1]. Other Notable Updates: - Features: Added experimental support for.svelte files [1]. - Bug Fixes: Added a space after commas in import attributes [1]. - Performance: Optimized nested configuration prescan and improved performance for single import runs and ImportDeclaration processing [1]. - Documentation: Included refreshed documentation for import sorting and other minor comment corrections [1].
Citations:
Update oxfmt dependency with awareness of breaking changes in 0.49.0.
Version 0.49.0 exists and is available on npm. Note that this release includes a breaking change: oxfmt now respects more git ignore options, aligning its behavior with oxlint. Verify that this behavior aligns with your project's expectations before deploying.
🤖 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 `@package.json` at line 20, package.json bumps the "oxfmt" dependency to
"^0.49.0", which contains a breaking change that makes oxfmt respect more
gitignore rules; confirm this change won't break formatting in your repo by
running the formatter and CI, and either pin to a safe prior version (e.g.,
change "oxfmt" to the previous semver) or update repo ignore/config files to
accommodate the new behavior; specifically, run oxfmt against the codebase,
check for missing files now ignored, adjust .gitignore or oxfmt config as
needed, update CHANGELOG or PR notes to call out the behavior change, and
add/adjust tests or CI formatting checks to guard against regressions.
|
|
||
| catalog: | ||
| "tailwindcss": ^4.1.18 | ||
| "tailwindcss": ^4.3.0 |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Tailwind CSS 4.3.0 release breaking changes
💡 Result:
Tailwind CSS v4.3.0 was released on May 8, 2026 [1][2][3]. While this release primarily introduces new features and improvements, it includes one notable deprecation that may affect existing codebases [2]. Deprecation: The legacy start-* and end-* utilities are now deprecated in favor of inset-s-* and inset-e-* [2]. This change was made to align the API with the existing inset-bs-* and inset-be-* utilities [2]. Other notable changes and additions include: - New scrollbar utilities (scrollbar-{auto,thin,none}, scrollbar-thumb-, scrollbar-track-, and scrollbar-gutter-) [1][2]. - New @container-size utility for creating size containers [2]. - New zoom- and tab-* utilities [2]. - Support for stacked and compound @variant definitions [2]. - Enhanced functional @utility definitions with --default value support [2]. The release also includes various fixes to the canonicalization process for arbitrary values and improvements to the @tailwindcss/vite plugin [1]. Users are encouraged to review the official release blog post for detailed examples of these new features [2].
Citations:
- 1: tailwindlabs/tailwindcss@588bd73
- 2: https://tailwindcss.com/blog/tailwindcss-v4-3
- 3: https://github.com/tailwindlabs/tailwindcss/releases/tag/v4.3.0
Check codebase for deprecated start- and end- utilities before upgrading to Tailwind CSS 4.3.0.**
Tailwind CSS 4.3.0 (released May 8, 2026) deprecates the legacy start-* and end-* utilities in favor of inset-s-* and inset-e-* for API alignment. Review the codebase for usage of these deprecated utilities and plan migration accordingly. The release also includes new features (scrollbar utilities, @container-size, zoom-, tab-) but no breaking changes beyond this deprecation.
🤖 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 `@pnpm-workspace.yaml` at line 9, The project is being upgraded to Tailwind CSS
4.3.0 which deprecates start-* and end-* utilities; search the codebase for any
usages of start-* and end-* (in templates, .css/.scss files, React/Vue/TSX/JSX
components and tailwind.config.js) and replace them with the new inset-s-* and
inset-e-* equivalents, update any custom plugin/shorthand definitions in
tailwind.config.js that emit start/end utilities to emit inset-s/inset-e, and
run the Tailwind build to verify no remaining references and that layout/rtl
behavior remains correct.
1 participant
Summary by CodeRabbit