[bulk] Add release-plan.yaml (2026-01-13-001)

[hdamker-bot]

Add release-plan.yaml for automated release tracking

This PR introduces release-plan.yaml — a metadata file that will replace manual wiki-based release tracking with automated tooling.

What is this?

The release-plan.yaml file declares your release intentions for this repository. It enables:

• Automated Release Progress Tracker (replacing wiki API tables)
• CI validation of release readiness
• Automated release branch creation (coming soon)

Pre-populated data

This file was generated from your latest release data and repository settings:

• APIs: From your most recent release (r2.2)
• Contacts: From your CODEOWNERS file

👉 Please review and adjust if API-specific contacts differ from repository-wide codeowners.

What to do now

Option A: Merge as-is (recommended if no immediate release planned)

• The file is pre-populated with your current release state (r2.2, Fall25)
• target_release_type: none means "no release currently planned"
• Just merge — the file will be updated when you plan your next release

Option B: Update before merging (if planning a release soon)

1. Set target_release_type to your intended release type
2. Update target_release_tag for your next release:
   • New cycle: increment first number, reset second to 1 (e.g., r3.2 → r4.1)
   • Progression in same cycle: increment second number (e.g., r3.2 → r3.3)
3. Update target_api_version for any APIs being changed
4. Optionally add meta_release: Fall26 if participating in the meta-release

Before your next release

Update this file with your release intentions:

repository:
  target_release_tag: rX.Y      # Your next release tag
  target_release_type: pre-release-alpha  # Or: pre-release-rc, public-release, maintenance-release

Documentation

📖 Full documentation (work in progress)
📖 Release Workflow and Metadata Specification
📖 API Versioning (in CAMARA API Design Guide)

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	2		0	0.01s
✅ API	spectral	3		0	4.78s
✅ GHERKIN	gherkin-lint	11		0	3.4s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	secretlint	yes		no	0.84s
✅ YAML	yamllint	3		0	0.96s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

[hdamker]

Test of workflow, closing.