From e77a01e1b2448bb2c0936a661bec71934e820f6d Mon Sep 17 00:00:00 2001 From: nmccready Date: Thu, 2 Jul 2026 23:12:13 -0400 Subject: [PATCH] docs: bump README version references 1.9.3 -> 1.10.2 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit npm latest dist-tag is 1.10.2 but the README (repo + npm) still advertises 1.9.3 in four places — install snippet, CDN URL, and the version callouts. Co-Authored-By: Claude Fable 5 --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 8388155c117..4c7376584fa 100644 --- a/README.md +++ b/README.md @@ -36,7 +36,7 @@ Most enterprises face three bad options: ✅ **Drop-in replacement** — Same API, same behavior, zero code changes ✅ **MIT licensed** — Free and open source, forever ✅ **Actively maintained** — CI/CD, npm provenance, GitHub security advisories -✅ **Production-ready** — Latest version **1.9.3** on npm +✅ **Production-ready** — Latest version **1.10.2** on npm **One command. Zero refactoring. Full security compliance.** @@ -80,14 +80,14 @@ Your `package.json` should now show: ```json { "dependencies": { - "@brickhouse-tech/angular-lts": "^1.9.3" + "@brickhouse-tech/angular-lts": "^1.10.2" } } ``` If you're using a CDN, point to: ```html - + ``` --- @@ -139,7 +139,7 @@ Every contribution helps keep this project alive for the thousands of teams stil ## Technical Details - **Upstream:** Based on `angular@1.8.3` (final official release) -- **Current version:** `1.9.3` (includes all security patches) +- **Current version:** `1.10.2` (includes all security patches) - **Testing:** CI via GitHub Actions, tested on Node 20+ - **Publishing:** OIDC npm publishing with provenance attestation - **License:** MIT (same as original AngularJS)