[docs] Update documentation for features from 2025-12-16#6703
Merged
Conversation
- Document new metadata field in frontmatter (from #6666) - Document HTTP authentication headers for MCP servers (from #6687) - Remove outdated URL parameter authentication reference 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
github-actions
Bot
added
automation
documentation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR documents two new features merged on December 16-17, 2025: a metadata frontmatter field for storing custom workflow information, and HTTP header authentication support for MCP servers.
- Added documentation for the
metadatafrontmatter field with key-value constraints - Added HTTP authentication headers configuration for MCP servers
- Removed outdated URL parameter authentication reference
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| docs/src/content/docs/reference/frontmatter.md | Documents the new metadata frontmatter field with usage examples and constraints for storing custom workflow metadata |
| docs/src/content/docs/guides/mcps.md | Documents HTTP header authentication for MCP servers and removes outdated URL parameter authentication reference |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+74
to
+81
| version: 1.0.0 | ||
| category: automation | ||
| ``` | ||
|
|
||
| **Constraints:** | ||
| - Keys: 1-64 characters | ||
| - Values: Maximum 1024 characters | ||
| - Only string values are supported |
There was a problem hiding this comment.
The constraint "Only string values are supported" may be misleading when the example shows a numeric version value (1.0.0). While YAML parsers will treat unquoted 1.0.0 as a string, this could cause confusion. Consider either:
- Updating the example to use quoted strings to be explicit:
version: "1.0.0" - Clarifying the constraint to specify that numeric values will be coerced to strings
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation Updates - December 16-17, 2025
This PR updates the documentation based on features merged in the last 24 hours.
Features Documented
Changes Made
docs/src/content/docs/reference/frontmatter.mdto document the newmetadatafield with constraints and usage examplesdocs/src/content/docs/guides/mcps.mdto document HTTP authentication headers for MCP serversMerged PRs Referenced
Notes
The fuzzy scheduling features (#6659, #6664, #6693) are already comprehensively documented in
docs/src/content/docs/reference/triggers.mdand did not require updates. This PR focuses on the two undocumented features: metadata field and MCP HTTP headers.