{
	"release_id": "4.3-20250925150428",
	"date": "2025-09-25T15:04:28.254769+00:00",
	"type": "service",
	"major_version": "4.3",
	"urgency": "medium",
	"text": {
		"de": "# opsi-utils und opsi-cli\n\n\"opsi-cli client-action set-action-request --where-outdated\" und der wrapper \"opsi-outdated-to-setup\" in opsi-utils nutzen eine statische Liste von excludes für Produkte. Diese greift auch, wenn keine excludes manuell angegeben wurden. Mit der heute releasten Version wurde die Liste dieser excludes um das Paket \"windows11-upgrade\" erweitert.\nDa in mehreren Umgebungen diese Befehle ohne weitere Einschränkung genutzt werden gehe ich die Änderung sofort nach stable frei (um zu verhindern, dass unnötig windows-updates gefahren werden).",
		"en": "# opsi-utils and opsi-cli\n\n\"opsi-cli client-action set-action-request --where-outdated\" and its wrapper \"opsi-outdated-to-setup\" in opsi-utils use a static list of excludes for products.\nThese are in effect even if no excludes are manually specified. With the version released today we extended this list by the package \"windows11-upgrade\".\nIn some environments these commands are used without additional filter. This is why I push this change directory to stable (to avoid unneccessary windows-update runs)."
	},
	"components": [
		{
			"name": "opsi-cli",
			"type": "OPSI_PACKAGE",
			"version": "4.3.29.2-1",
			"removal": false,
			"changelog_url": "OPSI_PACKAGE/opsi-cli/changelog.txt",
			"version_text_de": "",
			"version_text_en": ""
		},
		{
			"name": "opsi-cli",
			"type": "TOOL",
			"version": "4.3.29.2",
			"removal": false,
			"changelog_url": "TOOL/opsi-cli/changelog.txt",
			"version_text_de": "",
			"version_text_en": ""
		},
		{
			"name": "opsi-utils",
			"type": "SERVER_PACKAGE",
			"version": "4.3.18.2",
			"removal": false,
			"changelog_url": "SERVER_PACKAGE/opsi-utils/changelog.txt",
			"version_text_de": "",
			"version_text_en": ""
		}
	]
}