chore: change source code license header

[xuthus5]

fix: #333

Summary by CodeRabbit

• Chores
  • Standardized copyright and licensing headers across the codebase by updating the formatting and attribution to "2025 Apollo Authors" while retaining the existing Apache License, Version 2.0 terms. These internal updates do not affect the application's functionality.

[coderabbitai]

Walkthrough

The changes in this pull request update the licensing header in a wide range of files across the project. Each file’s multi‐line comment block previously attributing copyright and licensing to the Apache Software Foundation has been replaced by a single‐line comment that states “Copyright 2025 Apollo Authors,” while retaining the Apache License, Version 2.0. No modifications were made to any code logic, exported entities, or control flow.

Changes

File(s)	Change Summary
agcache/{cache.go, memory/memory.go, memory/memory_test.go}	Reformatted licensing header: replaced multi-line ASF block with single-line “Copyright 2025 Apollo Authors” maintaining Apache License 2.0.
client.{go,test.go}	Updated licensing header to single-line format with revised copyright attribution.
cluster/{load_balance.go, roundrobin/round_robin.go, roundrobin/round_robin_test.go}	Changed multi-line ASF license comments to single-line comments with “Copyright 2025 Apollo Authors.”
component/{common.go, common_test.go, log/{log.go, log_test.go}, notify/{change_event_test.go, componet_notify.go, componet_notify_test.go, mock_server_test.go}, remote/{abs.go, async.go, async_test.go, remote.go, sync.go, sync_test.go}, serverlist/{app_config_server_test.go, sync.go, sync_test.go}}	Updated licensing headers across all files from ASF multi-line blocks to concise single-line comments with new copyright.
constant/config_file_format.go	Revised licensing header formatting to single-line comment with updated copyright.
env/{app_config.go, app_config_test.go, config/{apollo_config.go, apollo_config_test.go, config.go, config_test.go, json/{json_config.go, json_config_test.go}}, file/{file_handler.go, json/{json.go, json_test.go, raw.go, raw_test.go}}, request_config.go, server/{server.go, server_test.go}}	Standardized header comments in all env files to single-line format with “Copyright 2025 Apollo Authors.”
extension/{cache.go, cache_test.go, file.{go, test.go}, format_parser.{go, test.go}, load_balance.{go, test.go}, sgin_test.go, sign.go}	Modified licensing headers from multi-line ASF blocks to single-line comments with new copyright.
mock_server_test.go	Converted licensing comment block to single-line comments with updated copyright.
protocol/{auth/{auth.go, sign/{sign.go, sign_test.go}}, http/{request.go, request_server_test.go, request_test.go}}	Replaced ASF-based multi-line licensing header with a simplified single-line comment reflecting the new copyright.
start.{go, test.go}	Completely replaced the ASF license header with a new single-line comment citing “Copyright 2025 Apollo Authors.”
storage/{change_event.{go, test.go}, event_dispatch.{go, test.go}, repository.{go, test.go}}	Updated licensing header by switching from multi-line ASF comments to single-line comments with updated copyright.
utils/{parse/{normal/{parser.go, parser_test.go}, parser.go, parse/properties/{parser.go, parser_test.go}, parse/yaml/{parser.go, parser_test.go}, parse/yml/{parser.go, parser_test.go}, utils.{go, utils_test.go}}	Replaced the existing multi-line license comment blocks with single-line comments that now attribute copyright to “2025 Apollo Authors.”

Assessment against linked issues

Objective	Addressed	Explanation
Update open source protocol license header (#333)	✅

Suggested reviewers

• hezhangjian

Poem

I'm just a bunny with hops so light,
Skipping through code in the pale moonlight.
Licensing headers now gleam so bright,
"2025 Apollo Authors" – oh what a sight!
With swift little hops, my joy takes flight.
Code and carrots, all feels just right!
🐰🌟

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[mergify]

感谢您提出Pull Request，我会尽快Review。我会在1-2日内进行查看或者回复，如果遇到节假日可能会处理较慢，敬请谅解。

[coveralls]

Pull Request Test Coverage Report for Build 14246489621

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 75.613%

---

Totals
Change from base Build 14243775028:	0.0%
Covered Lines:	1327
Relevant Lines:	1755

---

💛 - Coveralls

[nobodyiam]

Thanks!