Update README.md

[boqiny]

User description

Description

Related Issue

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Code refactoring
• Performance improvement

How Has This Been Tested?

Screenshots (if applicable)

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Additional Notes

---

PR Type

Documentation

---

Description

• Added notice about backend stack update (June 2025)

• Prompted users to regenerate their API key

---

Changes walkthrough 📝

	Relevant files
Documentation	README.md Add backend update notice                                                                README.md Inserted a new markdown note about backend stack update date Advised users to generate a new API key from the provided link +2/-0

---

Need help?

Type /help how to ... in the comments thread for any questions about PR-Agent usage.

Check out the documentation for more information.

[Copilot]

Pull Request Overview

This PR updates the README.md to inform users about the updated backend stack and the need to generate a new API key.

• Added a note regarding the backend update and API key regeneration.

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Correct date preposition Change the preposition "on June 2025" to "in June 2025" for correct English usage when referring to a month and year. README.md [10] -### Note: We recently updated our backend stack on June 2025, please generate a new API Key from the link below! +### Note: We recently updated our backend stack in June 2025, please generate a new API Key from the link below! Suggestion importance[1-10]: 5 __ Why: Using “in June 2025” instead of “on June 2025” fixes the grammatical preposition for month-year references and improves readability.	Low
	Fix extra heading space Remove the extra space after the heading marker to conform to standard Markdown heading syntax. This ensures consistent rendering across Markdown parsers. README.md [10] -### Note: We recently updated our backend stack on June 2025, please generate a new API Key from the link below! +### Note: We recently updated our backend stack on June 2025, please generate a new API Key from the link below! Suggestion importance[1-10]: 3 __ Why: Removing the double space after the heading marker ensures consistent Markdown syntax and rendering across parsers.	Low
	Normalize API key casing Use consistent capitalization for "API key" to match the rest of the document and standard terminology. README.md [10] -### Note: We recently updated our backend stack in June 2025, please generate a new API Key from the link below! +### Note: We recently updated our backend stack in June 2025, please generate a new API key from the link below! Suggestion importance[1-10]: 3 __ Why: Lowercasing “key” aligns with the document’s terminology and maintains consistent capitalization for “API key”.	Low