Skip to content

Conversation

@hamideh-amini-khezrabad
Copy link
Contributor

WHAT is this change about?

This change updates the release-candidate branch to align the stemcell version with the main branch. It ensures consistency between the two branches.

What customer problem is being addressed? Use customer persona to define the problem e.g. Alana is unable to...

It ensures consistency between the two branches.

Has a cf-deployment including this change passed cf-acceptance-tests?

  • YES
  • NO

Does this PR introduce a breaking change? Please take a moment to read through the examples before answering the question.

  • YES - please choose the category from below. Feel free to provide additional details.
  • NO

Types of breaking changes:

  1. causes app or operator downtime
  2. increases VM footprint of cf-deployment - e.g. new jobs, new add ons, increases # of instances etc.
  3. modifies, deletes or moves the name of a job or instance group in the main manifest
  4. modifies the name or deletes a property of a job or instance group in the main manifest
  5. changes the name of credentials in the main manifest
  6. requires out-of-band manual intervention on the part of the operator
  7. modifies the ops-file path, changes the type, changes the values or removes ops-files from the following folders
    • ./operations/ or ./operations/experimental
    • ./addons
    • ./backup-and-restore/

If you're promoting an experimental Ops-file (or removing one), Please follow the Ops-file workflows.

Ops files changes in the following folders are considered as NON BREAKING CHANGES
./community, ./example-vars-files, ./test

How should this change be described in cf-deployment release notes?

Does this PR introduce a new BOSH release into the base cf-deployment.yml manifest or any ops-files?

  • YES - please specify
  • NO

Does this PR make a change to an experimental or GA'd feature/component?

  • experimental feature/component
  • GA'd feature/component

Please provide Acceptance Criteria for this change?

Run check-stemcell-versions task as green

What is the level of urgency for publishing this change?

  • Urgent - unblocks current or future work
  • Slightly Less than Urgent

@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Feb 12, 2026

CLA Signed

@hamideh-amini-khezrabad hamideh-amini-khezrabad marked this pull request as ready for review February 12, 2026 15:34
@hamideh-amini-khezrabad hamideh-amini-khezrabad changed the base branch from release-candidate to develop February 12, 2026 15:52
@hamideh-amini-khezrabad hamideh-amini-khezrabad changed the title Update release candidate Manual merge stemcell version update from main Feb 12, 2026
@hamideh-amini-khezrabad hamideh-amini-khezrabad deleted the update-release-candidate branch February 13, 2026 07:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant