chore: update readme

[hrishikesh-k]

Just adding some version notes

[netlify]

✅ Deploy Preview for angular-runtime-demo ready!

Name	Link
🔨 Latest commit	4c94f36
🔍 Latest deploy log	https://app.netlify.com/projects/angular-runtime-demo/deploys/6a20397e27cd2300075e5cdf
😎 Deploy Preview	https://deploy-preview-446--angular-runtime-demo.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 896ed4e5-1875-49bb-bee4-d6194ebe2ebf

📥 Commits

Reviewing files that changed from the base of the PR and between 23a888e and 4c94f36.

📒 Files selected for processing (1)

• README.md

---

📝 Walkthrough

Summary by CodeRabbit

• Documentation
  • Updated Installation and Configuration guidance to clarify support for Angular 19 and later versions.

Walkthrough

This PR updates the README's Installation and Configuration section heading. The text "For Angular 19 and Angular 20" is replaced with "For Angular 19+" to provide broader version guidance while retaining the existing Netlify configuration note beneath it.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'chore: update readme' is vague and generic, using non-descriptive terms that don't convey the specific change being made (updating Angular version guidance from '19 and 20' to '19+').	Consider a more specific title like 'chore: update Angular version guidance in README' to better describe the actual change.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description 'Just adding some version notes' is related to the changeset as the PR does add version guidance, but it is vague and doesn't convey meaningful details about what version notes were added or changed.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch hk/angular-version-readme

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}