upgrade apollo version to 2.4.0

[nobodyiam]

Summary by CodeRabbit

• Chores
  • Updated release and application versions for Apollo Portal and Apollo Service to reflect the latest deployment state.
• Documentation
  • Enhanced chart entries with refreshed metadata and updated timestamps, ensuring users have access to the most current release information.

[coderabbitai]

Walkthrough

This pull request updates the version information for the apollo-portal and apollo-service Helm charts. In both Chart.yaml files, the version is incremented from 0.9.0 to 0.10.0, and the appVersion from 2.3.0 to 2.4.0. Additionally, the docs/index.yaml file now includes new entries for these charts with updated metadata and creation timestamps, reflecting the revised versions.

Changes

File(s)	Change Summary
apollo-portal/Chart.yaml apollo-service/Chart.yaml	Updated version from 0.9.0 to 0.10.0 and appVersion from 2.3.0 to 2.4.0 in both Helm chart files.
docs/index.yaml	Added new metadata entries for both charts with updated apiVersion: v2, creation timestamps, digest values, and version: 0.10.0.

Possibly related PRs

• ci: 更新 Helm chart 仓库索引 #20: Updates to docs/index.yaml metadata fields are closely related, reflecting similar versioning and chart metadata modifications.
• feat(charts): 在服务模板中添加 annotations 配置支持 #19: Updates to the apollo-portal/Chart.yaml version field show a direct correlation with the current version increments.

Poem

I'm a bunny with a skip in my hop,
Versions leaped forward, no chance to stop!
Chart files updated with numbers so bright,
Docs now gleam with metadata light.
Happy hops through Helm chart streams,
Celebrating code in whimsical dreams!
🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

docs/index.yaml (2)

3-307: Consistent Update of 'created' Timestamps in Apollo-Portal Entries
Multiple entries under the apollo-portal key have updated created timestamps (e.g., lines 6, 22, 38, 54, 70, … up to line 307). This appears to be the result of regenerating the index file.
Please verify that these timestamps accurately represent the timing of the release and that the time zone or formatting meets your expectations.

---

325-612: Consistent Update of 'created' Timestamps in Apollo-Service Entries
Similarly, many entries for apollo-service (after the new entry) show updated created timestamps (for example, lines 327, 343, 359, 375, … up to line 612).
Ensure these updates are intentional and consistent with your CI/CD pipeline’s timestamp generation.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 61429d3 and d05e063.

📒 Files selected for processing (3)

• apollo-portal/Chart.yaml (1 hunks)
• apollo-service/Chart.yaml (1 hunks)
• docs/index.yaml (37 hunks)

✅ Files skipped from review due to trivial changes (2)

• apollo-service/Chart.yaml
• apollo-portal/Chart.yaml

🔇 Additional comments (3)

docs/index.yaml (3)

4-19: New Apollo-Portal Entry with Upgraded Version
This new top entry for apollo-portal now reflects the updated release details:

• appVersion is updated to 2.4.0 (in line with the PR objective)
• version is updated to 0.10.0
• The created timestamp is newly set to a current value.

Everything in this block appears consistent with the intended upgrade. Please verify that all Helm chart metadata for apollo-portal has been updated accordingly.

---

308-324: New Apollo-Service Chart Entry Added
A new entry for apollo-service has been introduced with the following details:

• appVersion is set to 2.4.0
• version is set to 0.10.0
• Associated metadata (including created, description, digest, etc.) is provided.

This addition meets the upgrade objective. Please ensure that the corresponding Helm chart files also reflect these changes.

---

613-614: Verify Generation Timestamp
The final generated field (line 613) is now set to "2025-02-10T21:10:58.941731+08:00". Please confirm that this generation timestamp correctly reflects the current build process.