docs: update changelog dates

[tonykipkemboi]

• Updated dates on Changelog
• Added Bedrock KB Tool & Bedrock Agents as a tool in the docs

[joaomdmoura]

Disclaimer: This review was made by a crew of AI Agents.

Code Review Comment for PR #2437 - Changelog Date Updates

Overview

This pull request updates the release dates in the changelog.mdx from 2023/2024 to 2024/2025, affecting 10 version entries. Below are my observations and recommendations based on the modifications made.

Positive Aspects

1. Consistent Formatting: The changelog format is uniformly applied, which greatly aids readability.
2. Semantic Versioning: The version numbers adhere to semantic versioning principles, clarifying the nature of changes.
3. Clear Change Categorization: Changes are effectively categorized into Features, Fixes, etc., enhancing user understanding.
4. Structural Integrity: The MDX components maintain their structural integrity, ensuring functionality.

Issues Identified

1. Chronological Order Inconsistency:

   • The release entries are now presented in a non-linear order, which could mislead users. It is advised to confirm if this arrangement was intentional.

2. Inconsistent Version Increments:
   The version increments show:

   v0.108.0 (March 2025)
   v0.105.0 (March 2025)
   v0.102.0 (February 2025)
   v0.100.0 (January 2025)
   

   Such patterns can cause confusion regarding the change history.

3. MDX Component Structure:
   The current structure:

   <Update label="2025-03-17" description="v0.108.0">

   Suggestion: To enhance clarity, consider including additional semantic metadata:

   <Update 
     label="2025-03-17" 
     version="v0.108.0"
     type="feature-release"
   >

Recommendations

1. Date Format Consistency:

   • Adopt ISO 8601 format (YYYY-MM-DD) across all entries for improved consistency.

   <Update label="2025-03-17" description="v0.108.0">

2. Enhance Version Documentation:
   Incorporate a version summary for each entry:

   <Update label="2025-03-17" description="v0.108.0">
     {/* Version Summary */}
     **Release Focus**: Enhanced LLM Integration and Developer Experience

3. Changelog Visual Structure:
   Utilize categorical emojis for easier scanning:

   <Update label="2025-03-17" description="v0.108.0">
     ✨ **Features**
     🐛 **Bug Fixes**
     📚 **Documentation**
     ⚡ **Performance**
   </Update>

4. Metadata Tracking:
   Add a YAML frontmatter for ongoing tracking:

   ---
   lastUpdated: '2025-03-21'
   versionRange: 'v0.80.0 - v0.108.0'
   totalReleases: 10
   ---

Quality Assurance Checklist

• Date format consistency.
• Version numbering correctness.
• MDX syntax compliance.
• Effective categorization.
• Logical progression of release dates.
• Consistent version increment patterns.

Additional Notes

1. The aim of this update appears to be preparing documentation for future releases.
2. Consider linking GitHub releases/tags in the changelog for better traceability.
3. Recommend including a "Breaking Changes" section in significant updates for user awareness.

This review underlines the need for improved documentation quality and consistency. Although the date updates are straightforward, the structural enhancements suggested will significantly enhance the clarity and usability of the changelog for all stakeholders.