chore(lcm): Bump up LCM version to release the Redshift boolean fix - #2122

No actionable comments were generated in the recent review.

Merge Risk: Minimal · up to dd280

No actionable code risk remains; the release version change is ready after normal checks.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title names the main change: bumping the LCM version so the Redshift boolean fix is released. The raw summary confirms VERSION moves from 3.7.112 to 3.7.113, and the objectives say this bump is wh…
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Title check

Explanation

The title names the main change: bumping the LCM version so the Redshift boolean fix is released. The raw summary confirms VERSION moves from 3.7.112 to 3.7.113, and the objectives say this bump is what triggers the image build that carries the fix. The title is short, single-sentence, and specific. The 'chore(lcm):' prefix is a conventional-commit scope and does not reduce clarity.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{A rabbit checks the version line,
From three-seven-one-one-two to three.
One small step marks the release,
Fresh carrots wait beside the code.
The bunny hops, the numbers shine.}

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Essentials
• Run ID: c6bac751-aa77-4b67-baa7-17092c4cdf7e

Commits

Reviewing files that changed from the base of the PR and between 704286f and dd280bf.

Files selected for processing: 1

• VERSION

Included review availability: This review used your included allowance. 4 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour.

LCM bricks image available

New image stable/lcm-bricks is available.

Next steps

1. Tag the image with its major version
Run the LCM: Retag stable image to major version workflow dispatch:

• Go to Actions → LCM: Retag stable image to major version → Run workflow
• Set tag to 3.7.113
• Leave dry-run unchecked and click Run workflow

Or via gh CLI:

gh workflow run lcm-stable-retag.yaml --repo gooddata/gooddata-ruby -f tag=3.7.113 -f dry-run=false

2. Register bricks to prod clusters
Once the retag completes, manually run the respective Rundeck job for each cluster: rundeck-sslauth.na.intgdc.com