-
Notifications
You must be signed in to change notification settings - Fork 43
Update recommended TG version #2840
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
WalkthroughThis pull request updates the Terragrunt version compatibility documentation by adding two new recommended version rows (0.93.1) to the existing compatibility tables for both GitHub and GitLab platforms, highlighting performance improvements for environment authentication. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes
Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
docs/2.0/reference/pipelines/terragrunt-version-compatibility.md (1)
11-11: Minor: Consider clarifying the performance improvement comment.The new rows look great and are positioned logically. The phrasing "Pipeline/Terragrunt is considerably faster on 0.93.1+ for environment auth" is a bit terse. Consider whether you'd like to elaborate slightly on what "environment auth" refers to (e.g., "environment variable authentication" or link to relevant docs if available) to help users understand the scope of the improvement.
That said, this is a documentation patch and may be fine as-is if it matches your project's style. Feel free to adjust if it would benefit from clarity.
Also applies to: 23-23
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/2.0/reference/pipelines/terragrunt-version-compatibility.md(2 hunks)
🧰 Additional context used
🧠 Learnings (2)
📚 Learning: 2025-07-17T18:44:16.153Z
Learnt from: ZachGoldberg
Repo: gruntwork-io/docs PR: 2663
File: docs/2.0/docs/pipelines/architecture/change-types.md:59-61
Timestamp: 2025-07-17T18:44:16.153Z
Learning: In current Terragrunt versions (2024-2025), the preferred command syntax is `terragrunt run --all` rather than the deprecated `terragrunt run-all` subcommand. The `run-all` command is still functional for backwards compatibility but is being phased out in favor of the `run --all` syntax.
Applied to files:
docs/2.0/reference/pipelines/terragrunt-version-compatibility.md
📚 Learning: 2025-07-23T21:18:35.163Z
Learnt from: CR
Repo: gruntwork-io/docs PR: 0
File: .cursor/rules/gitlab-background.mdc:0-0
Timestamp: 2025-07-23T21:18:35.163Z
Learning: Applies to docs/**/*.mdx : Whenever presenting information that diverges between GitHub and GitLab, use the <Tabs> and <TabItem> components to distinguish the two sets of information UNLESS the distinction is just changing one word. For example, GitHub has pull requests and GitLab has merge requests, so we can just say '... pull/merge requests...' and not need full <Tabs>.
Applied to files:
docs/2.0/reference/pipelines/terragrunt-version-compatibility.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: Validate generated content
- GitHub Check: validate_build
Summary by CodeRabbit