updating compose for v6.27

[epag]

Description

[Short description explaining the high-level reason for the pull request]

Changes Made

Testing

Related Tickets

• Fixes [Ticket number]

Checklists

Deployment Plan (For developer use)

How does the changes affect the product?

• Feature addition
• Bug fix
• Database change

Issuer Checklist (For developer use)

You may update this checklist before and/or after creating the PR. If you're unsure about any of them, please ask, we're here to help! These items are what we are going to look for before merging your code.

• Informative and human-readable title, using the format: [_pt] PR: <description>
• Links are provided if this PR resolves an issue, or depends on another other PR
• The feature branch you're submitting as a PR is up to date
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• No Placeholder code
• Reviewers requested
• Add yourself as an assignee in the PR

Merge Checklist (For Technical Lead use only)

• If applicable, update README with major alterations