Skip to content

fix(web): link release notes to GitHub - #2114

Merged
kevincodex1 merged 2 commits into
Twigpine:mainfrom
jatmn:fix/web-release-0.28.0
Aug 12, 2026
Merged

kevincodex1 merged 2 commits into
Twigpine:mainfrom
jatmn:fix/web-release-0.28.0

Conversation

@jatmn

@jatmn jatmn commented Aug 11, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • remove the locally maintained “what’s new” page and release-data source
  • link every release-notes entry point to GitHub Releases in a new tab
  • preserve existing /changelog/ URLs with a noindex redirect to GitHub Releases

Root cause

The static changelog duplicated release data, made the displayed version stale,
and added an unrelated npm-registry dependency to web builds. GitHub Releases
is the canonical release-notes source.

Validation

  • bun test web/scripts/verify-dist.test.ts
  • bun run --cwd web typecheck
  • bun run --cwd web build

Summary by CodeRabbit

  • New Features

    • Added direct links to GitHub Releases from the main navigation, footer, and documentation.
    • External release links now open safely in a new tab.
    • Added a redirect from the legacy changelog page to GitHub Releases.
  • Updates

    • Removed displayed application version labels from the site header, footer, and terminal demo.
    • External release links are excluded from documentation page navigation.
  • Documentation

    • Updated release guidance to use GitHub Releases as the central source for release notes.

@coderabbitai

coderabbitai Bot commented Aug 11, 2026 •

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: e5123da7-7e37-476b-a9df-115fa99d347f

📥 Commits

Reviewing files that changed from the base of the PR and between 78038c3 and d719a9d.

📒 Files selected for processing (2)
  • web/scripts/verify-dist.test.ts
  • web/scripts/verify-dist.ts
📜 Recent review details
⏰ Context from checks skipped due to timeout. (3)
  • GitHub Check: typecheck
  • GitHub Check: smoke-and-tests (22)
  • GitHub Check: smoke-and-tests (24.11.x)
🧰 Additional context used
📓 Path-based instructions (4)
**/*.{ts,tsx}

📄 CodeRabbit inference engine (AGENTS.md)

**/*.{ts,tsx}: Use TypeScript with strict mode and ESM imports.
Use existing patterns in the file or nearby module rather than introducing unrelated abstractions or broad rewrites.
Add or update tests when behavior changes.
Use React and Ink conventions for terminal UI components.

Files:

  • web/scripts/verify-dist.test.ts
  • web/scripts/verify-dist.ts
web/**/*.{ts,tsx}

📄 CodeRabbit inference engine (AGENTS.md)

Run the web typecheck and build checks when touching website code.

Files:

  • web/scripts/verify-dist.test.ts
  • web/scripts/verify-dist.ts
**/*

📄 CodeRabbit inference engine (AGENTS.md)

Keep changes focused on one problem and avoid unrelated formatting, renames, dependency changes, or broad rewrites.

Follow the existing code style in touched files, keep comments useful and concise, and do not reformat unrelated files.

Files:

  • web/scripts/verify-dist.test.ts
  • web/scripts/verify-dist.ts

⚙️ CodeRabbit configuration file

**/*: Apply the OpenClaude maintainer review rubric from AGENTS.md. Review the current diff, not stale discussion context. Separate real blockers from suggestions. Do not request changes for vague style churn. Treat approval as merge-ready from CodeRabbit's side, pending required human review and GitHub Checks. If checks are failing or unavailable, say so clearly instead of implying the PR is fully ready.

Files:

  • web/scripts/verify-dist.test.ts
  • web/scripts/verify-dist.ts
web/**

⚙️ CodeRabbit configuration file

web/**: Review browser extension changes for content-script isolation, message validation, cross-origin assumptions, permission surfaces, and failures that could leak prompts or credentials.

Files:

  • web/scripts/verify-dist.test.ts
  • web/scripts/verify-dist.ts
🧠 Learnings (10)
📓 Common learnings
Learnt from: CR
Repo: Gitlawb/openclaude PR: 0
File: CONTRIBUTING.md:0-0
Timestamp: 2026-08-07T01:57:16.417Z
Learning: Applies to web/src/data/releases.ts : Do not edit `web/src/data/releases.ts` during ordinary feature or bug-fix work; only modify it in an explicit release/web changelog PR.
Learnt from: CR
Repo: Gitlawb/openclaude PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-08-07T01:57:07.096Z
Learning: Applies to web/src/data/releases.ts : Do not edit `web/src/data/releases.ts` in ordinary feature or bugfix PRs; it is owned by the release/web process.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:41.682Z
Learning: Update documentation when setup, commands, provider behavior, or other user-facing behavior changes.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:41.682Z
Learning: For new features, larger refactors, dependency changes, or runtime changes, follow the issue-first guidance in `CONTRIBUTING.md`.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:41.682Z
Learning: Do not add new Python code, Python provider paths, or Python dependencies without explicit maintainer approval.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:41.682Z
Learning: Do not skip tests for behavior changes.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:41.682Z
Learning: Do not silently change provider tags; maintainers control them during review.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:41.682Z
Learning: Address CodeRabbit and maintainer feedback before requesting more review.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:41.682Z
Learning: Do not add a manually maintained release-notes data source to the static site; link to GitHub Releases instead.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:49.625Z
Learning: Keep pull requests focused on one problem or one clearly scoped improvement; avoid unrelated cleanup, fixes, features, or refactors.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:49.625Z
Learning: Preserve existing repository patterns unless intentionally refactoring them, and prefer small, readable changes over broad rewrites.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:49.625Z
Learning: Add or update tests when a change affects behavior.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:49.625Z
Learning: Update documentation when setup, commands, or user-facing behavior changes.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:49.625Z
Learning: Do not add manually maintained release-note data or a local changelog page to the static site; link release-notes navigation to GitHub Releases.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:49.625Z
Learning: Review AI-generated changes for correctness, unnecessary changes, style consistency, and adherence to project architecture before submitting them.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:49.625Z
Learning: Stay within the project's existing technical direction; changes to the language, core runtime, or dependency stack require prior maintainer agreement.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:49.625Z
Learning: Dependency changes must provide a concrete project benefit, such as fixing a bug, addressing a security issue, or supporting an approved feature.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:49.625Z
Learning: Provider changes must avoid breaking third-party providers while fixing first-party behavior, test the exact provider/model path when possible, and document affected providers and limitations.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:49.625Z
Learning: Do not assign or use provider tags; provider tags are controlled and applied by maintainers.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:49.625Z
Learning: Run the narrowest meaningful validation command for the touched area before opening a pull request.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:49.625Z
Learning: Run relevant CI checks locally before pushing; pull requests that fail CI checks will not be merged.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:49.625Z
Learning: Run web typechecking and web builds when touching the `web/` area.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-12T00:13:49.625Z
Learning: For security reports, follow `SECURITY.md` rather than submitting the details through the normal contribution process.
📚 Learning: 2026-08-07T01:57:16.417Z
Learnt from: CR
Repo: Gitlawb/openclaude PR: 0
File: CONTRIBUTING.md:0-0
Timestamp: 2026-08-07T01:57:16.417Z
Learning: Applies to web/src/data/releases.ts : Do not edit `web/src/data/releases.ts` during ordinary feature or bug-fix work; only modify it in an explicit release/web changelog PR.

Applied to files:

  • web/scripts/verify-dist.test.ts
  • web/scripts/verify-dist.ts
📚 Learning: 2026-08-07T01:57:07.096Z
Learnt from: CR
Repo: Gitlawb/openclaude PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-08-07T01:57:07.096Z
Learning: Applies to web/src/data/releases.ts : Do not edit `web/src/data/releases.ts` in ordinary feature or bugfix PRs; it is owned by the release/web process.

Applied to files:

  • web/scripts/verify-dist.test.ts
  • web/scripts/verify-dist.ts
📚 Learning: 2026-08-07T01:57:07.096Z
Learnt from: CR
Repo: Gitlawb/openclaude PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-08-07T01:57:07.096Z
Learning: Applies to **/*.{test,spec}.{ts,tsx} : Add or update tests when behavior changes, and run the narrowest useful focused test checks.

Applied to files:

  • web/scripts/verify-dist.test.ts
  • web/scripts/verify-dist.ts
📚 Learning: 2026-08-07T01:57:16.417Z
Learnt from: CR
Repo: Gitlawb/openclaude PR: 0
File: CONTRIBUTING.md:0-0
Timestamp: 2026-08-07T01:57:16.417Z
Learning: Applies to **/*.{test,spec}.{ts,tsx,js,jsx} : Add or update tests when a code change affects behavior.

Applied to files:

  • web/scripts/verify-dist.test.ts
  • web/scripts/verify-dist.ts
📚 Learning: 2026-08-07T01:57:16.417Z
Learnt from: CR
Repo: Gitlawb/openclaude PR: 0
File: CONTRIBUTING.md:0-0
Timestamp: 2026-08-07T01:57:16.417Z
Learning: Applies to **/*.{test,spec}.{ts,tsx,js,jsx} : Use focused tests such as `bun test ./path/to/test-file.test.ts` when validating a narrowly scoped change.

Applied to files:

  • web/scripts/verify-dist.test.ts
📚 Learning: 2026-06-17T03:03:34.545Z
Learnt from: CR
Repo: Gitlawb/openclaude PR: 0
File: coderabbit-custom-pre-merge-checks-unique-id-file-non-traceable-F7F2B60C-1728-4C9A-8889-4F2235E186CA.txt:0-0
Timestamp: 2026-06-17T03:03:34.545Z
Learning: Verify that product, trust-model, routing-default, telemetry/network, and permission-policy changes are not hidden inside unrelated cleanup. Flag the PR if the policy decision needs explicit maintainer alignment.

Applied to files:

  • web/scripts/verify-dist.test.ts
  • web/scripts/verify-dist.ts
📚 Learning: 2026-08-07T01:57:16.417Z
Learnt from: CR
Repo: Gitlawb/openclaude PR: 0
File: CONTRIBUTING.md:0-0
Timestamp: 2026-08-07T01:57:16.417Z
Learning: Applies to **/*.{ts,tsx,js,jsx} : Review AI-assisted code for correctness, style consistency, unnecessary changes, and adherence to project architecture before submitting it.

Applied to files:

  • web/scripts/verify-dist.test.ts
  • web/scripts/verify-dist.ts
📚 Learning: 2026-08-07T01:57:16.417Z
Learnt from: CR
Repo: Gitlawb/openclaude PR: 0
File: CONTRIBUTING.md:0-0
Timestamp: 2026-08-07T01:57:16.417Z
Learning: Applies to **/*.{ts,tsx,js,jsx} : Follow the existing code style in touched source files, prefer small readable changes, avoid unrelated reformatting, and keep comments useful and concise.

Applied to files:

  • web/scripts/verify-dist.test.ts
📚 Learning: 2026-08-07T01:57:16.417Z
Learnt from: CR
Repo: Gitlawb/openclaude PR: 0
File: CONTRIBUTING.md:0-0
Timestamp: 2026-08-07T01:57:16.417Z
Learning: Applies to **/*.{ts,tsx} : Run `bun run typecheck` and `bun run typecheck:type-tests` for TypeScript changes when applicable.

Applied to files:

  • web/scripts/verify-dist.test.ts
🔇 Additional comments (2)
web/scripts/verify-dist.ts (1)

3-9: LGTM!

Also applies to: 36-59, 81-81, 90-97

web/scripts/verify-dist.test.ts (1)

2-8: LGTM!

Also applies to: 20-30, 40-40, 54-54, 74-117, 128-128, 141-147


📝 Walkthrough

Walkthrough

The web site removes local changelog and npm freshness validation. Release navigation now targets GitHub Releases, the legacy changelog route redirects there, version displays are removed, and contributor guidance is updated.

Changes

GitHub Releases migration

Layer / File(s) Summary
GitHub Releases navigation contract
web/src/data/site.ts, web/src/data/docsNav.ts, web/src/components/*, web/src/pages/docs/index.astro, web/src/pages/index.astro
Release links use SITE.releasesUrl and open in new tabs. Documentation pagination excludes external release links. Site version displays and metadata are removed.
Legacy redirect and distribution verification
web/astro.config.mjs, web/scripts/verify-dist.ts, web/scripts/verify-dist.test.ts
The legacy changelog route redirects to GitHub Releases. Distribution checks now validate release links, buddy navigation, routes, and the reduced sitemap. npm freshness and local release-data checks are removed.
Release maintenance guidance
AGENTS.md, CONTRIBUTING.md
Guidance directs release notes and release navigation to GitHub Releases instead of local changelog data.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Possibly related PRs

Suggested labels: bug

Suggested reviewers: kevincodex1

🚥 Pre-merge checks | ✅ 5 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 33.33% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Risk Surface Disclosed ⚠️ Warning The PR changes outbound behavior by removing the npm registry fetch and adding GitHub redirect links, but the description does not explicitly assess the risk surface or state whether a blocker exists. Add a risk section that names the removed npm fetch and external GitHub redirect/link behavior, then state clearly whether these changes introduce a blocker.
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title is concise, scoped to web changes, and accurately describes linking release notes to GitHub.
Description check ✅ Passed The description explains the change and rationale and lists validation commands, but it does not use all template headings.
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.
No Hidden Policy Change ✅ Passed The diff makes release-source, redirect, new-tab, and npm-registry network changes explicit in the PR scope; no separate trust, permission, telemetry, or routing policy is hidden in cleanup.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@web/src/data/releases.ts`:
- Around line 24-35: Update the PR validation report associated with the release
entry to explicitly list the focused web commands bun run web:typecheck and bun
run web:build, and run both checks before reporting them.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: f8c58d4e-441e-4721-be6f-b10acf2c0bee

📥 Commits

Reviewing files that changed from the base of the PR and between 6e30b40 and 4b62ca9.

📒 Files selected for processing (1)
  • web/src/data/releases.ts
📜 Review details
⏰ Context from checks skipped due to timeout. (3)
  • GitHub Check: smoke-and-tests (24.11.x)
  • GitHub Check: smoke-and-tests (22)
  • GitHub Check: typecheck
🧰 Additional context used
📓 Path-based instructions (8)
**/*.{ts,tsx}

📄 CodeRabbit inference engine (AGENTS.md)

Use TypeScript strict mode and ESM imports throughout the source code.

Run bun run typecheck and bun run typecheck:type-tests for TypeScript changes when applicable.

Files:

  • web/src/data/releases.ts
**/*.{tsx,ts}

📄 CodeRabbit inference engine (AGENTS.md)

Use React and Ink patterns for terminal UI components.

Files:

  • web/src/data/releases.ts
web/**/*.{ts,tsx}

📄 CodeRabbit inference engine (AGENTS.md)

When changing the web application, run the web typecheck and build checks.

Files:

  • web/src/data/releases.ts
web/src/data/releases.ts

📄 CodeRabbit inference engine (AGENTS.md)

Do not edit web/src/data/releases.ts in ordinary feature or bugfix PRs; it is owned by the release/web process.

Do not edit web/src/data/releases.ts during ordinary feature or bug-fix work; only modify it in an explicit release/web changelog PR.

Files:

  • web/src/data/releases.ts
**/*.{ts,tsx,js,jsx}

📄 CodeRabbit inference engine (AGENTS.md)

Do not add new Python code, Python provider paths, or Python dependencies without explicit maintainer approval.

**/*.{ts,tsx,js,jsx}: Follow the existing code style in touched source files, prefer small readable changes, avoid unrelated reformatting, and keep comments useful and concise.
Preserve existing repository patterns unless intentionally refactoring them, and avoid broad rewrites or unnecessary generated changes.
Review AI-assisted code for correctness, style consistency, unnecessary changes, and adherence to project architecture before submitting it.

Files:

  • web/src/data/releases.ts
**/*

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Update documentation when setup, commands, or user-facing behavior changes.

Files:

  • web/src/data/releases.ts

⚙️ CodeRabbit configuration file

**/*: Apply the OpenClaude maintainer review rubric from AGENTS.md. Review the current diff, not stale discussion context. Separate real blockers from suggestions. Do not request changes for vague style churn. Treat approval as merge-ready from CodeRabbit's side, pending required human review and GitHub Checks. If checks are failing or unavailable, say so clearly instead of implying the PR is fully ready.

Files:

  • web/src/data/releases.ts
web/**/*

📄 CodeRabbit inference engine (CONTRIBUTING.md)

When changing files under web/, run bun run web:typecheck and bun run web:build.

Files:

  • web/src/data/releases.ts
web/**

⚙️ CodeRabbit configuration file

web/**: Review browser extension changes for content-script isolation, message validation, cross-origin assumptions, permission surfaces, and failures that could leak prompts or credentials.

Files:

  • web/src/data/releases.ts

Comment thread web/src/data/releases.ts Outdated
@jatmn jatmn self-assigned this Aug 11, 2026
@jatmn
jatmn force-pushed the fix/web-release-0.28.0 branch from 4b62ca9 to c248098 Compare August 11, 2026 21:56
@jatmn jatmn changed the title fix(web): add 0.28.0 changelog entry fix(web): isolate npm freshness from PR builds Aug 11, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/web-release-freshness.yml:
- Around line 15-16: Update the actions/checkout step in the web release
freshness workflow to set persist-credentials to false, ensuring later Bun steps
cannot access persisted checkout credentials; leave the existing checkout action
and other options unchanged.

In `@web/scripts/verify-dist.test.ts`:
- Line 175: Extend the verification tests around the existing “release/web
process” assertion to cover the CHECK_NPM_FRESHNESS gate, including its enabled
and disabled behavior and expected failure handling.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: a851396f-92bf-4848-b4bf-812ffb3609cc

📥 Commits

Reviewing files that changed from the base of the PR and between 4b62ca9 and c248098.

📒 Files selected for processing (4)
  • .github/workflows/web-release-freshness.yml
  • web/scripts/verify-dist.test.ts
  • web/scripts/verify-dist.ts
  • web/src/data/releases.ts
📜 Review details
⏰ Context from checks skipped due to timeout. (3)
  • GitHub Check: smoke-and-tests (22)
  • GitHub Check: smoke-and-tests (24.11.x)
  • GitHub Check: typecheck
🧰 Additional context used
📓 Path-based instructions (11)
**/*.{ts,tsx}

📄 CodeRabbit inference engine (AGENTS.md)

Use TypeScript strict mode and ESM imports throughout the source code.

Run bun run typecheck and bun run typecheck:type-tests for TypeScript changes when applicable.

Files:

  • web/scripts/verify-dist.ts
  • web/src/data/releases.ts
  • web/scripts/verify-dist.test.ts
**/*.{tsx,ts}

📄 CodeRabbit inference engine (AGENTS.md)

Use React and Ink patterns for terminal UI components.

Files:

  • web/scripts/verify-dist.ts
  • web/src/data/releases.ts
  • web/scripts/verify-dist.test.ts
web/**/*.{ts,tsx}

📄 CodeRabbit inference engine (AGENTS.md)

When changing the web application, run the web typecheck and build checks.

Files:

  • web/scripts/verify-dist.ts
  • web/src/data/releases.ts
  • web/scripts/verify-dist.test.ts
**/*.{ts,tsx,js,jsx}

📄 CodeRabbit inference engine (AGENTS.md)

Do not add new Python code, Python provider paths, or Python dependencies without explicit maintainer approval.

**/*.{ts,tsx,js,jsx}: Follow the existing code style in touched source files, prefer small readable changes, avoid unrelated reformatting, and keep comments useful and concise.
Preserve existing repository patterns unless intentionally refactoring them, and avoid broad rewrites or unnecessary generated changes.
Review AI-assisted code for correctness, style consistency, unnecessary changes, and adherence to project architecture before submitting it.

Files:

  • web/scripts/verify-dist.ts
  • web/src/data/releases.ts
  • web/scripts/verify-dist.test.ts
**/*

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Update documentation when setup, commands, or user-facing behavior changes.

Files:

  • web/scripts/verify-dist.ts
  • web/src/data/releases.ts
  • web/scripts/verify-dist.test.ts

⚙️ CodeRabbit configuration file

**/*: Apply the OpenClaude maintainer review rubric from AGENTS.md. Review the current diff, not stale discussion context. Separate real blockers from suggestions. Do not request changes for vague style churn. Treat approval as merge-ready from CodeRabbit's side, pending required human review and GitHub Checks. If checks are failing or unavailable, say so clearly instead of implying the PR is fully ready.

Files:

  • web/scripts/verify-dist.ts
  • web/src/data/releases.ts
  • web/scripts/verify-dist.test.ts
web/**/*

📄 CodeRabbit inference engine (CONTRIBUTING.md)

When changing files under web/, run bun run web:typecheck and bun run web:build.

Files:

  • web/scripts/verify-dist.ts
  • web/src/data/releases.ts
  • web/scripts/verify-dist.test.ts
web/**

⚙️ CodeRabbit configuration file

web/**: Review browser extension changes for content-script isolation, message validation, cross-origin assumptions, permission surfaces, and failures that could leak prompts or credentials.

Files:

  • web/scripts/verify-dist.ts
  • web/src/data/releases.ts
  • web/scripts/verify-dist.test.ts
.github/**

⚙️ CodeRabbit configuration file

.github/**: Review CI and release workflow changes for token permissions, third-party actions, pull_request_target usage, artifact upload/download behavior, shell injection, and whether checks still run on the actual PR head. Block on broadened write permissions or unpinned/excessively trusted external execution unless clearly justified.

Files:

  • .github/workflows/web-release-freshness.yml
web/src/data/releases.ts

📄 CodeRabbit inference engine (AGENTS.md)

Do not edit web/src/data/releases.ts in ordinary feature or bugfix PRs; it is owned by the release/web process.

Do not edit web/src/data/releases.ts during ordinary feature or bug-fix work; only modify it in an explicit release/web changelog PR.

Files:

  • web/src/data/releases.ts
**/*.{test,spec}.{ts,tsx}

📄 CodeRabbit inference engine (AGENTS.md)

Add or update tests when behavior changes, and run the narrowest useful focused test checks.

Files:

  • web/scripts/verify-dist.test.ts
**/*.{test,spec}.{ts,tsx,js,jsx}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

**/*.{test,spec}.{ts,tsx,js,jsx}: Add or update tests when a code change affects behavior.
Use focused tests such as bun test ./path/to/test-file.test.ts when validating a narrowly scoped change.

Files:

  • web/scripts/verify-dist.test.ts
🪛 zizmor (1.29.0)
.github/workflows/web-release-freshness.yml

[warning] 15-16: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false

(artipacked)


[info] 12-12: workflow or action definition without a name (anonymous-definition): this job

(anonymous-definition)


[warning] 3-6: insufficient job-level concurrency limits (concurrency-limits): workflow is missing concurrency setting

(concurrency-limits)

🔇 Additional comments (2)
web/scripts/verify-dist.ts (1)

98-99: LGTM!

Also applies to: 113-122

web/src/data/releases.ts (1)

143-144: LGTM!

Comment thread .github/workflows/web-release-freshness.yml Outdated
Comment thread web/scripts/verify-dist.test.ts Outdated
@jatmn
jatmn force-pushed the fix/web-release-0.28.0 branch from c248098 to 78038c3 Compare August 11, 2026 22:25
@jatmn jatmn changed the title fix(web): isolate npm freshness from PR builds fix(web): link release notes to GitHub Aug 11, 2026
@jatmn
jatmn marked this pull request as ready for review August 11, 2026 23:12

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@web/scripts/verify-dist.ts`:
- Around line 46-51: Update verifyDist in web/scripts/verify-dist.ts at lines
46-51 to require target="_blank" and rel="noopener" on both release links, and
require noindex on the legacy changelog redirect output. Update the valid
fixture in web/scripts/verify-dist.test.ts at lines 20-30 with these attributes,
then add mutation cases removing each attribute and assert verification fails.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2f1a15ae-67a1-41e0-bcf8-4a256bcb08b4

📥 Commits

Reviewing files that changed from the base of the PR and between c248098 and 78038c3.

📒 Files selected for processing (14)
  • AGENTS.md
  • CONTRIBUTING.md
  • web/astro.config.mjs
  • web/scripts/verify-dist.test.ts
  • web/scripts/verify-dist.ts
  • web/src/components/DocsSidebar.astro
  • web/src/components/Footer.astro
  • web/src/components/Nav.astro
  • web/src/data/docsNav.ts
  • web/src/data/releases.ts
  • web/src/data/site.ts
  • web/src/pages/changelog.astro
  • web/src/pages/docs/index.astro
  • web/src/pages/index.astro
💤 Files with no reviewable changes (2)
  • web/src/pages/changelog.astro
  • web/src/data/releases.ts
📜 Review details
🧰 Additional context used
📓 Path-based instructions (6)
web/**/*

📄 CodeRabbit inference engine (AGENTS.md)

Run web typecheck and build validation when changing files under web/.

Files:

  • web/src/components/DocsSidebar.astro
  • web/astro.config.mjs
  • web/src/pages/docs/index.astro
  • web/src/components/Nav.astro
  • web/src/pages/index.astro
  • web/src/data/site.ts
  • web/src/data/docsNav.ts
  • web/src/components/Footer.astro
  • web/scripts/verify-dist.ts
  • web/scripts/verify-dist.test.ts
**/*

📄 CodeRabbit inference engine (AGENTS.md)

**/*: Run the narrowest useful validation checks for each change and list the exact commands in the PR.
Do not add a manually maintained release-notes data source to the static site; link to GitHub Releases instead.

**/*: Keep pull requests focused on one problem or feature, and avoid mixing unrelated cleanup or refactors.
Preserve existing repository patterns unless intentionally refactoring them.
Update documentation when setup, commands, or user-facing behavior changes.
Do not add manually maintained release-note data to the static site; link release-notes navigation to GitHub Releases.
Review AI-generated changes for correctness, style consistency, unnecessary changes, and adherence to project architecture before submitting them.
Follow the existing code style in touched files.
Prefer small, readable changes over broad rewrites.
Do not reformat unrelated files.
Keep comments useful and concise.
Provider changes must avoid breaking third-party providers while fixing first-party behavior.
When changing provider behavior, test the exact provider/model path changed when possible and document affected providers, limitations, and follow-up work.
Do not assign or use provider tags; provider tags are controlled by maintainers.
Run the narrowest meaningful validation command for the touched area, and do not merge changes that fail CI checks.

Files:

  • web/src/components/DocsSidebar.astro
  • web/astro.config.mjs
  • web/src/pages/docs/index.astro
  • AGENTS.md
  • web/src/components/Nav.astro
  • web/src/pages/index.astro
  • web/src/data/site.ts
  • web/src/data/docsNav.ts
  • web/src/components/Footer.astro
  • web/scripts/verify-dist.ts
  • web/scripts/verify-dist.test.ts
  • CONTRIBUTING.md

⚙️ CodeRabbit configuration file

**/*: Apply the OpenClaude maintainer review rubric from AGENTS.md. Review the current diff, not stale discussion context. Separate real blockers from suggestions. Do not request changes for vague style churn. Treat approval as merge-ready from CodeRabbit's side, pending required human review and GitHub Checks. If checks are failing or unavailable, say so clearly instead of implying the PR is fully ready.

Files:

  • web/src/components/DocsSidebar.astro
  • web/astro.config.mjs
  • web/src/pages/docs/index.astro
  • AGENTS.md
  • web/src/components/Nav.astro
  • web/src/pages/index.astro
  • web/src/data/site.ts
  • web/src/data/docsNav.ts
  • web/src/components/Footer.astro
  • web/scripts/verify-dist.ts
  • web/scripts/verify-dist.test.ts
  • CONTRIBUTING.md
web/**

⚙️ CodeRabbit configuration file

web/**: Review browser extension changes for content-script isolation, message validation, cross-origin assumptions, permission surfaces, and failures that could leak prompts or credentials.

Files:

  • web/src/components/DocsSidebar.astro
  • web/astro.config.mjs
  • web/src/pages/docs/index.astro
  • web/src/components/Nav.astro
  • web/src/pages/index.astro
  • web/src/data/site.ts
  • web/src/data/docsNav.ts
  • web/src/components/Footer.astro
  • web/scripts/verify-dist.ts
  • web/scripts/verify-dist.test.ts
**/*.{ts,tsx}

📄 CodeRabbit inference engine (AGENTS.md)

**/*.{ts,tsx}: Use TypeScript with strict mode and ESM imports.
Prefer existing service, provider, settings, permission, and UI patterns over introducing new abstractions.

Files:

  • web/src/data/site.ts
  • web/src/data/docsNav.ts
  • web/scripts/verify-dist.ts
  • web/scripts/verify-dist.test.ts
**/*.{ts,tsx,js,jsx}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Add or update tests when a code change affects behavior.

Files:

  • web/src/data/site.ts
  • web/src/data/docsNav.ts
  • web/scripts/verify-dist.ts
  • web/scripts/verify-dist.test.ts
{README.md,CONTRIBUTING.md,docs/**,.github/pull_request_template.md}

⚙️ CodeRabbit configuration file

{README.md,CONTRIBUTING.md,docs/**,.github/pull_request_template.md}: Review docs for accuracy against current code behavior. Flag security or provider claims that overpromise, stale install commands, missing setup caveats, and instructions that could push users toward unsafe credential handling. Keep purely wording-level suggestions non-blocking.

Files:

  • CONTRIBUTING.md
🧠 Learnings (1)
📓 Common learnings
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-11T23:12:52.725Z
Learning: Keep changes focused on one problem and avoid unrelated formatting, renames, dependency changes, or broad rewrites.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-11T23:12:52.725Z
Learning: Add or update tests when behavior changes.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-11T23:12:52.725Z
Learning: Update documentation when setup, commands, provider behavior, or user-facing behavior changes.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-11T23:12:52.725Z
Learning: Do not change the Node.js runtime or Bun development workflow without prior maintainer agreement.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-11T23:12:52.725Z
Learning: Do not skip tests for behavior changes.
Learnt from: CR
Repo: Gitlawb/openclaude

Timestamp: 2026-08-11T23:12:52.725Z
Learning: Address CodeRabbit or maintainer feedback before requesting more review.
🪛 LanguageTool
AGENTS.md

[style] ~104-~104: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ess it before requesting more review. - Do not add a manually maintained release-n...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

🔇 Additional comments (10)
AGENTS.md (1)

77-77: LGTM!

Also applies to: 104-104

CONTRIBUTING.md (1)

136-136: LGTM!

Also applies to: 154-154

web/src/data/site.ts (1)

10-10: LGTM!

web/src/data/docsNav.ts (1)

1-6: LGTM!

Also applies to: 37-43

web/src/components/DocsSidebar.astro (1)

15-15: LGTM!

web/src/components/Footer.astro (1)

27-27: LGTM!

Also applies to: 57-57, 67-68

web/src/components/Nav.astro (1)

8-8: LGTM!

Also applies to: 21-28, 39-39

web/src/pages/docs/index.astro (1)

41-41: LGTM!

web/src/pages/index.astro (1)

104-104: LGTM!

web/astro.config.mjs (1)

7-9: LGTM!

Comment thread web/scripts/verify-dist.ts Outdated

@jatmn jatmn left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kevincodex1 LGTM
Will make the site more basic for now when it comes to release notes.. but also prevents alot of slop in the notes as well as the current ci issues on main

@kevincodex1
kevincodex1 merged commit c40d663 into Twigpine:main Aug 12, 2026
6 checks passed
@kevincodex1

Copy link
Copy Markdown
Member

will redeploy the site in a bit

@jatmn
jatmn deleted the fix/web-release-0.28.0 branch August 12, 2026 00:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants