Skip to content

v5.1.2 — Star-History chart fix (revert broken hosted embed)

Choose a tag to compare

View all tags
@AleksNeStu AleksNeStu released this 15 Aug 18:34
· 41 commits to dev since this release
v5.1.2
4324a7e

v5.1.2 — Star-History chart fix (revert broken hosted embed)

Release date: 2026-08-15
Type: Patch (documentation fix, no code change)

Fix

The v5.1.1 release introduced a hosted api.star-history.com/svg embed that turned out to be broken at the upstream level for this repo:

  • Returns the "GitHub restricted access to star data" placeholder image regardless of token configuration
  • Verified live 2026-08-15 with ?secret=<fine-grained-PAT> using the same GITHUB_TOKEN_AVN PAT that successfully hits GET /repos/AleksNeStu/ai-real-estate-assistant/stargazers (200 OK with data)
  • The star-history.com service is broken for non-trivial star data per their own blog post

This patch reverts to the working img.shields.io star badge + a note documenting the upstream issue. The shields badge correctly shows the current star count of 294.

Carried-forward from v5.1.1

  • 6 Dependabot HIGH + 1 MEDIUM CVEs closed (package.json overrides for js-yaml 3.x/4.x, nanoid, dompurify; extract-zip dismissed as tolerable_risk)
  • CodeQL config error fixed (removed conflicting queries: security-extended input that conflicted with config-file per codeql-action docs)
  • ESLint: disabled 4 new opt-in react-hooks rules (set-state-in-effect, static-components, immutability, preserve-manual-memoization) bumped in via the new eslint-plugin-react-hooks version pulled in by the overrides
  • Private Vulnerability Reporting enabled for AleksNeStu/ai-real-estate-assistant and AleksNeStu/ai-news-scraper (via PUT /repos/{owner}/{repo}/private-vulnerability-reporting)

Roadmap

  • v5.2+: working self-hosted star-history chart (requires the upstream GitHub restriction to be resolved, or a switch to a different chart service that doesn't depend on the stargazer API)
  • Re-enable the 4 disabled ESLint rules per-page after refactoring to SWR / React Query (imperative useEffect(() => fetch().then(setState)) blocks)
  • extract-zip Dependabot alert #313 — re-open if upstream releases a fix; currently dev-only via @lhci/utils → inquirer → external-editor
  • Mirror-only repos (cv, natively-cluely, EBiCS_Firmware) — enable Private Vulnerability Reporting separately on dev-scaler + nest-ai-dev (these repos don't exist on AleksNeStu)

Verification

  • CI green: 15/15 jobs on commit 4324a7e (gitleaks, secret-validation, backend-lint, backend-tests unit+integration, frontend-build, frontend-tests, e2e, codeql-python, codeql-javascript, security-sast, security-deps, container-scan, lighthouse, compose_smoke, pipeline-health)
  • 0 open PRs, 0 open Dependabot alerts, 0 open CodeQL alerts at release time
  • The img.shields.io/github/stars/AleksNeStu/ai-real-estate-assistant?style=social badge in README now shows 294 stars correctly

Migration notes

  • No data migration.
  • No API change.
  • No breaking config change.
  • README change is documentation-only.
  • The asset/my-star-history/star-history-{light,dark}.svg files on the star-history orphan branch (last commit ba1d657) are now stale (only contain growth-metrics.json from the v5.1.1 soft-fail run). The branch is no longer referenced by README. The orphan branch is harmless but can be deleted via git push origin --delete star-history when convenient.

Credits

  • Per star-history.com blog for the workaround documentation.
  • shields.io for the static star badge fallback.
Assets 2
Loading