[bulk] Enable release automation and validation

[camara-release-automation]

Enable CAMARA Validation and Release Automation for DeviceLocation

Following the Spring26 release announcement on the codeowners list, this PR applies the following changes to your DeviceLocation repository:

• installs the CAMARA Validation workflow
• installs the CAMARA Release Automation workflow
• creates the new CHANGELOG directory structure

What you get

CAMARA Validation will run automatically on every PR against main, release-snapshot/**, or maintenance/**:

• Catches compliance and spec issues at PR time, when fixes are cheap
• Annotates changed files inline in the PR (in "files changed" view)
• Provides a detailed report on the workflow run page
• Same set of validation rules applied to all CAMARA APIs, kept current with each Commonalities release

Release Automation simplifies creating the release of an API version:

• Automates the tedious tasks of creating a release — version bumps, CHANGELOG entry collection, release metadata
• Slash ("/") commands on Release Issues give explicit control over the steps in the release process (e.g. snapshotting, publishing, and rollback)
• Consistent quality across all CAMARA APIs through predictable, repeatable release process.

Changes

File	Description
.github/workflows/camara-validation.yml	CAMARA Validation caller (pinned to @v1-rc)
.github/workflows/release-automation.yml	Release Automation caller (pinned to @v1-rc)
CHANGELOG.md	Added forward-reference note
CHANGELOG/README.md	Created index file (with historical reference)

What to do next

Merge this PR to activate the full validation and automation processes.

After the merge you can prepare and create a release as follows:

1. Plan — update release-plan.yaml with target release tag, type, and API versions/statuses
2. Develop — continue work on main keeping version fields always set to wip
3. Snapshot — post /create-snapshot on the Release Issue to generate a Release PR
4. Review & Merge — review Release PR (includes CHANGELOG entry), obtain approvals, merge it
5. Publish — post /publish-release --confirm rX.Y to finalize the release

If issues arise: use /discard-snapshot (during review) or /delete-draft (during draft) to return to planned state.

More: Release Process

---

After merge, the admin team will disable the legacy validation workflow from the repository.

Questions or feedback? See the announcement for contact channels (Zulip, GitHub issues, mailing list).

Documentation

📖 Validation on PRs — what to expect
📖 Where to see results
📖 Problem messages explained
📖 FAQ
📖 Release Management Documentation

[camara-validation]

CAMARA Validation — PASS

0 errors, 35 warnings, 23 hints | Profile: standard

View full results

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	4		0	0.01s
✅ API	spectral	3		0	3.65s
✅ GHERKIN	gherkin-lint	3		0	0.89s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	secretlint	yes		no	0.53s
✅ YAML	yamllint	3		0	0.65s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by