Adjust release process after quickstart changes

[schustmi]

Describe changes

The new quickstart doesn't include running on a cloud stack anymore. This PR removes any files/code that was still building Docker images for that purpose.

Note: We still run the quickstart on cloud stacks as part of the release process.

Pre-requisites

Please ensure you have done the following:

• I have read the CONTRIBUTING.md document.
• I have added tests to cover my changes.
• I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
• IMPORTANT: I made sure that my changes are reflected properly in the following resources:
  • ZenML Docs
  • Dashboard: Needs to be communicated to the frontend team.
  • Templates: Might need adjustments (that are not reflected in the template tests) in case of non-breaking changes and deprecations.
  • Projects: Depending on the version dependencies, different projects might get affected.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Other (add details above)

[github-actions]

Documentation Link Check Results

✅ Absolute links check passed
✅ Relative links check passed
_{Last checked: 2025-10-27 12:48:56 UTC}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	transformers@​4.28.1
	torch@​2.9.0
	setuptools@​80.9.0
	transformers@​4.57.1
	sagemaker@​2.253.1
	zenml@​0.91.0
	torchvision@​0.24.0
	qwen-agent@​0.0.31
	strands-agents-tools@​0.2.12
	scikit-learn@​1.5.0
	scikit-learn@​1.7.2
	scikit-learn@​1.6.0rc1
	torchaudio@​2.9.0
	semantic-kernel@​1.37.0
	session-info@​1.0.0
	sqlalchemy@​2.0.44
	uvicorn@​0.38.0
	rich@​14.2.0
	tox@​4.32.0
	pyyaml-include@​2.0b2
	tldextract@​5.1.3
	seaborn@​0.13.2
	yamlfix@​1.19.0
	sqlalchemy-utils@​0.42.0
	types-certifi@​2021.10.8.3
	s3fs@​2025.9.0
	requests@​2.32.5
	typing-extensions@​4.15.0
	strands-agents@​1.13.0
	ruff@​0.14.2
	pyyaml@​6.0.3
	types-termcolor@​1.1.6.2
	types-python-slugify@​8.0.2.20240310
See 18 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		transformers@4.28.1 has a Critical CVE. CVE: GHSA-3863-2447-669p transformers has a Deserialization of Untrusted Data vulnerability (CRITICAL) Affected versions: < 4.36.0 Patched version: 4.36.0 From: ? → pypi/transformers@4.28.1 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/transformers@4.28.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report