The September 2026 release replaced the connections: and artifacts: blocks in a bundle's massdriver.yaml with dependencies: and resources:, which carry a resource type version. The legacy blocks still publish, with a deprecation warning, and a slot declared that way takes part in no version checks.
The reference pages were updated in #223. These pages still teach the legacy format in their examples:
Two are out of scope for a hand edit and need their source changed instead:
docs/bundle-development/01-bundle-yaml-spec.md keeps both blocks on purpose — it documents the legacy format as deprecated.docs/reference/cli/commands/mass_bundle_new.md is generated from the CLI. If mass bundle new still scaffolds the legacy blocks, that belongs in the CLI repo.
Each conversion needs a resource type version to be correct, not just a key rename. $ref: aws-vpc becomes resource_type: aws-vpc@~1, and the required: list becomes a per-entry required: true/false flag, so the versions in each example have to be chosen against what the catalog actually publishes.
Refs #223
The September 2026 release replaced the
connections:andartifacts:blocks in a bundle'smassdriver.yamlwithdependencies:andresources:, which carry a resource type version. The legacy blocks still publish, with a deprecation warning, and a slot declared that way takes part in no version checks.The reference pages were updated in #223. These pages still teach the legacy format in their examples:
docs/applications/02-create-application.mddocs/bundle-development/provisioners/02-opentofu.mddocs/bundle-development/provisioners/03-terraform.mddocs/bundle-development/provisioners/04-helm.mddocs/bundle-development/provisioners/05-bicep.mddocs/bundle-development/publishing/01-bundle-templates.mddocs/bundle-development/publishing/02-module-patterns.mddocs/bundle-development/schema-design/02-massdriver-annotations.mddocs/guides/custom_artifact_definition.mddocs/platform-operations/self-hosted/05-dynamic-credentials.mdTwo are out of scope for a hand edit and need their source changed instead:
docs/bundle-development/01-bundle-yaml-spec.mdkeeps both blocks on purpose — it documents the legacy format as deprecated.docs/reference/cli/commands/mass_bundle_new.mdis generated from the CLI. Ifmass bundle newstill scaffolds the legacy blocks, that belongs in the CLI repo.Each conversion needs a resource type version to be correct, not just a key rename.
$ref: aws-vpcbecomesresource_type: aws-vpc@~1, and therequired:list becomes a per-entryrequired: true/falseflag, so the versions in each example have to be chosen against what the catalog actually publishes.Refs #223