chore: update lcore image to 0.7.0

[Jdubrick]

Target branch

• I have verified this PR targets the correct branch (see branching strategy)

Description

• Updates LCORE image to 0.7.0 release

Which issue(s) does this PR fix or relate to

• Fixes #issue_number

PR acceptance criteria

• Tests updated and passing
• Documentation updated
• Built-in TechDocs updated if needed. Note that TechDocs changes may need to be reviewed by a Product Manager and/or Architect to ensure content accuracy, clarity, and alignment with user needs.

How to test changes / Special notes to the reviewer

[rhdh-qodo-merge]

PR Summary by Qodo

Update the default Lightspeed Core image to 0.7.0

⚙️ Configuration changes 🕐 Less than 5 minutes

AI Description

• Use the official Lightspeed Core 0.7.0 image by default instead of a development build.
• Preserve the LIGHTSPEED_CORE_IMAGE override for deployments that need another image.

High-Level Assessment

Changing the Compose default is the direct approach: it adopts the release image without removing the existing environment-variable override.

Files changed (1) +2 / -2

Other (1) +2 / -2

compose.yamlSet the default Lightspeed Core image to 0.7.0 +2/-2

Set the default Lightspeed Core image to 0.7.0

• Replaces the development image tag with the official 0.7.0 release and updates the adjacent comment. The 'LIGHTSPEED_CORE_IMAGE' override remains available.

compose.yaml

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rhdh-qodo-merge]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. Setup docs still advertise the older image 🐞 Bug ⚙ Maintainability

Description

The maintenance guide still states that Compose defaults to lightspeed-stack:0.5.1 and uses
0.6.0 as its newer-image example. Users following that guide can select obsolete image tags or
misunderstand which LCORE release the repository currently runs.

Code

compose.yaml[R77-80]

+  # Default image: quay.io/lightspeed-core/lightspeed-stack:0.7.0
  # To override: Set LIGHTSPEED_CORE_IMAGE in your .env file
  lightspeed-core:
-    image: ${LIGHTSPEED_CORE_IMAGE:-quay.io/lightspeed-core/lightspeed-stack:dev-20260824-cbd182b} # dclint disable-line service-image-require-explicit-tag #todo: change tag to official release when available
+    image: ${LIGHTSPEED_CORE_IMAGE:-quay.io/lightspeed-core/lightspeed-stack:0.7.0} # dclint disable-line service-image-require-explicit-tag

Relevance

●●● Strong

Historical precedent accepts documentation fixes aligning examples and configuration with current
image or release behavior.

PR-#149
PR-#61

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The Compose file now identifies 0.7.0 as both the default image and the release available to
users, while the maintenance guide still says the default is 0.5.1 and shows 0.6.0 as the newer
version. These conflicting repository instructions are introduced by changing the Compose default
without updating the directly related documentation.

compose.yaml[77-80]
docs/intelligent-assistant/maintaining-intelligent-assistant.md[84-87]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The Compose default image was updated to `quay.io/lightspeed-core/lightspeed-stack:0.7.0`, but the maintenance guide still documents `0.5.1` as the default and `0.6.0` as the example override.

## Fix Focus Areas
- docs/intelligent-assistant/maintaining-intelligent-assistant.md[84-87]

## Recommended Fix
Update the documented default and override example to reflect the `0.7.0` release, while preserving the instructions for setting `LIGHTSPEED_CORE_IMAGE` to a custom or alternate image.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Dismiss ↗ | View ↗

---

Context sources

✅ Cross-repo context — repo relationships

  Explored: repo: redhat-developer/rhdh (sha: 049671d6) — View relationship

Review mode: 🚀 Fast: This is a localized, two-line container image tag update in compose.yaml with no security-sensitive or cross-cutting logic changes.

Tip of the day

💡 Did you know, you can show, collapse, or hide each part of a finding: code, evidence, and all

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[rhdh-qodo-merge]

Important

The /generate_labels command by Qodo is sunsetting on the 1st of October 2026 and will no longer be available. We recommend switching to the latest Qodo review capabilities. Learn more

[Jdubrick]

/cc @rm3l

[rm3l]

/cherrypick release-2.1

[openshift-cherrypick-robot]

@rm3l: new pull request created: #337

Details

In response to this:

/cherrypick release-2.1

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.