chore: release: bump to 0.44.0-dev in main

[btjd]

What does this PR do?

Bumps the version in the main branch to 0.44.0-dev following the creation of the 0.43.x release branch for v0.43.0.

What issues does this PR fix or reference?

N/A (Standard release cycle version bump)

Is it tested? How?

N/A - Routine version bump.

Summary by CodeRabbit

• Release
  • Updated the DevWorkspace Operator development release version to 0.44.0-dev.
  • Version information is now consistent across deployment metadata and displayed release details.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 7bee7785-7696-4e2a-8377-d495b4be4766

📥 Commits

Reviewing files that changed from the base of the PR and between 7cc5b95 and 8095de2.

📒 Files selected for processing (3)

• deploy/bundle/manifests/devworkspace-operator.clusterserviceversion.yaml
• deploy/templates/components/csv/clusterserviceversion.yaml
• version/version.go

---

📝 Walkthrough

Walkthrough

The operator development version is bumped from 0.43.0-dev to 0.44.0-dev in the Go version metadata and both ClusterServiceVersion declarations.

Changes

Development version bump

Layer / File(s)	Summary
Synchronize operator version metadata version/version.go, deploy/templates/components/csv/clusterserviceversion.yaml, deploy/bundle/manifests/devworkspace-operator.clusterserviceversion.yaml	Updates the exported version and ClusterServiceVersion identifiers to 0.44.0-dev.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• devfile/devworkspace-operator#1629: Performs a similar OLM development version bump.
• devfile/devworkspace-operator#1657: Updates the same version metadata files for a successive development release.

Suggested labels: lgtm

Suggested reviewers: ibuziuk, rohankanojia, akurinnoy, dkwon17

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the release version bump to 0.44.0-dev on main.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci-bump-main-0.44.0-dev

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[tolusha]

Hi! I'm che-ai-assistant — I help with your pull requests.

Available commands:

• /che-ai-assistant generate-che-doc — Generate a documentation PR based on this PR's changes
• /che-ai-assistant ok-pr-review — Run a comprehensive PR review (summary, code review, deep review, impact analysis)
• /che-ai-assistant ok-pr-readiness — Ensure PR has validation steps
• /che-ai-assistant check-pr-test-failures — Analyze failing CI checks, identify root causes, and suggest fixes
• /che-ai-assistant update-che-e2e-tests — Update Eclipse Che e2e tests
• /che-ai-assistant claude — Run a free-form instruction on this PR
• /che-ai-assistant help — Show this help message

[tolusha]

/che-ai-assistant ok-pr-readiness

Task completed.

[tolusha]

PR Readiness Assessment: PR #1678 — chore: release: bump to 0.44.0-dev in main

Repository: devfile/devworkspace-operator
Linked Issue: None found (N/A — standard release cycle version bump)

---

#	Criterion	Verdict	Notes
1	Problem Statement	PASS	PR clearly states it bumps the version in main to 0.44.0-dev following the creation of the 0.43.x release branch for v0.43.0.
2	Reproduction Steps	PASS	Relaxed — this is a routine version bump with no bug to reproduce. The context (release branch creation) is stated.
3	Expected Behavior After Fix	PASS	Relaxed — the expected outcome is self-evident: all version references should read 0.44.0-dev.
4	Scope of Changes	PASS	3 files changed, all with a single version string substitution (0.43.0-dev → 0.44.0-dev). Changes are minimal and fully consistent: two CSV manifests and version/version.go. No unrelated modifications.
5	Test Evidence	PASS	Relaxed — no logic change; this is a mechanical version string update. Existing CI checks are sufficient.
6	Deployment & Verification Notes	PASS	Relaxed — standard version bump requires no special deployment steps. The change is picked up automatically by the build pipeline.

Overall: ✅ READY

---

Missing Information

• None — all information needed for a routine version bump is present.

What's Good

• PR title and description clearly communicate the purpose and context of the change (release branch creation for v0.43.0).
• Changes are minimal, focused, and easy to verify at a glance — only version strings are updated.
• All three version references (clusterserviceversion.yaml bundle, CSV template, and version/version.go) are updated consistently.
• Correctly marked as N/A for testing and linked issues, which is appropriate for this type of mechanical change.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: btjd, dkwon17

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [dkwon17]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment