Default to shared bundle filename pattern

[lcawl]

This PR is an optional follow-up to #3984

Summary

The option-mode of the changelog bundle command now uses the same {repo}-{product}-{version}.yaml naming as profile mode when --output is omitted or is a directory.

Details

Behavior

• Explicit .yml / .yaml --output is unchanged.
• A directory --output (or no --output) joins the conventional name under that directory, bundle.output_directory, or the input directory.
• Product/version come from --output-products, then --input-products, then --release-version.
• If those cannot be resolved (--all, PR-only, and similar), the command warns and writes changelog-bundle.yaml.
• --plan gets the same product lists and --release-version, so output_path matches the run.

The pattern is as follows:

• Default (including option mode with no --output, or a directory) is {repo}-{product}-{version}.yaml.
• An explicit option-mode --output file path (with .yml or .yml filename) is used as-is.
• No authoring repo → warn and {product}-{version}.yaml.
• No product or version → warn and changelog-bundle.yaml.

Examples

I tried it out with some simple bundle commands like this:

.artifacts/publish/docs-builder/release/docs-builder changelog bundle --prs ./docs/temp/prs.txt --output-products "kibana" --output ./docs/releases/kibana/

Yields the same changelog-bundle.yaml file as previous, but with additional message: Could not resolve a product and version for the bundle file (pass --output-products or --input-products with a concrete target). Using 'changelog-bundle.yaml'.

If I run the command with sufficient info to follow the shared pattern, however, it works. For example:

.artifacts/publish/docs-builder/release/docs-builder changelog bundle --prs ./docs/temp/prs.txt --output-products "cloud-serverless 2026-08-31" --output ./docs/releases/kibana/

... now yields a docs/releases/kibana/kibana-cloud-serverless-2026-08-31.yaml file, same as the profile mode does.

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes
• No

2. If you answered "Yes" to the previous question, please specify the tool(s) and model(s) used (e.g., Google Gemini, OpenAI ChatGPT-4, etc.).

Tool(s) and model(s) used: Cursor Grok 4.6

[github-actions]

Docs preview (local build)

Handbook preview: https://docs-v3-preview.elastic.dev/elastic/docs-builder/pull/3985/

Sample changed pages:

• docs/cli/changelog/cmd-upload.md
• docs/data/release-notes/configure-ref.md