Skip to content

Release git-cas v6.5.6 - #113

Merged
flyingrobots merged 2 commits into
mainfrom
release/v6.5.6
Jul 30, 2026
Merged

Release git-cas v6.5.6#113
flyingrobots merged 2 commits into
mainfrom
release/v6.5.6

Conversation

@flyingrobots

Copy link
Copy Markdown
Member

Publishes the Bijou 7 hosted cockpit and deterministic checked-ref conflict classification.

Validation: 14/14 release gates; 6,898 observed tests across Node, Bun, and Deno; npm and JSR dry-runs passed.

@flyingrobots flyingrobots self-assigned this Jul 30, 2026
@coderabbitai

coderabbitai Bot commented Jul 30, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 46c2ab67-1ef1-4bbe-a2e0-ea620bb1c511

📥 Commits

Reviewing files that changed from the base of the PR and between 4327eff and d0a54df.

📒 Files selected for processing (18)
  • BEARING.md
  • CHANGELOG.md
  • README.md
  • ROADMAP.md
  • STATUS.md
  • UPGRADING.md
  • docs/design/0055-internal-commit-identity/witness/release-publication.md
  • docs/design/0056-bijou-7-framed-cockpit/bijou-7-framed-cockpit.md
  • docs/design/0057-deterministic-ref-conflict-posture/deterministic-ref-conflict-posture.md
  • docs/design/0057-deterministic-ref-conflict-posture/witness/release-candidate.md
  • docs/design/README.md
  • docs/releases/v6.5.6.md
  • jsr.json
  • package.json
  • src/package-version.js
  • test/unit/docs/package-docs.test.js
  • test/unit/docs/release-state.test.js
  • test/unit/docs/release-truth.test.js
📜 Recent review details
🧰 Additional context used
📓 Path-based instructions (6)
docs/design/**

📄 CodeRabbit inference engine (AGENTS.md)

Use docs/design/ directory for durable design contracts and proof plans

Files:

  • docs/design/0055-internal-commit-identity/witness/release-publication.md
  • docs/design/README.md
  • docs/design/0057-deterministic-ref-conflict-posture/witness/release-candidate.md
  • docs/design/0057-deterministic-ref-conflict-posture/deterministic-ref-conflict-posture.md
  • docs/design/0056-bijou-7-framed-cockpit/bijou-7-framed-cockpit.md
ROADMAP.md

📄 CodeRabbit inference engine (AGENTS.md)

Use ROADMAP.md as a signpost to the GitHub release tracker

Files:

  • ROADMAP.md
BEARING.md

📄 CodeRabbit inference engine (AGENTS.md)

Use BEARING.md to document current execution gravity and active tensions

Files:

  • BEARING.md
README.md

📄 CodeRabbit inference engine (AGENTS.md)

Use README.md as the public front door, core value prop, and quick start documentation

Files:

  • README.md
STATUS.md

📄 CodeRabbit inference engine (AGENTS.md)

Use STATUS.md as a compact snapshot of release and runtime truth

Files:

  • STATUS.md
CHANGELOG.md

📄 CodeRabbit inference engine (AGENTS.md)

Use CHANGELOG.md to record the historical truth of merged behavior

Files:

  • CHANGELOG.md
🧠 Learnings (3)
📚 Learning: 2026-07-13T17:00:46.222Z
Learnt from: flyingrobots
Repo: git-stunts/git-cas PR: 65
File: src/domain/helpers/isCanonicalCollectionKey.js:21-35
Timestamp: 2026-07-13T17:00:46.222Z
Learning: In git-stunts/git-cas, the codebase is intended to run on multiple JavaScript runtimes (Node, Bun, and Deno), not just Node. During code review, don’t suggest replacing existing portable helper logic with newer Node-only built-ins (e.g., Node 20+ APIs like `String.prototype.isWellFormed()`) unless the change preserves Bun/Deno compatibility (via portable/polyfill implementations or safe runtime gating). If a file includes manual implementations (such as `src/domain/helpers/isCanonicalCollectionKey.js`), treat them as intentional to avoid requiring a higher host built-in baseline.

Applied to files:

  • src/package-version.js
📚 Learning: 2026-02-28T19:21:13.982Z
Learnt from: flyingrobots
Repo: git-stunts/git-cas PR: 15
File: test/unit/domain/services/CasService.envelope.test.js:326-330
Timestamp: 2026-02-28T19:21:13.982Z
Learning: In fuzz tests for cryptographic operations, use a seeded PRNG (e.g., xorshift32) for control-flow variables such as plaintext size selection and recipient index selection to ensure reproducibility. Continue to use randomBytes() for cryptographic keys and nonces to preserve realistic randomness and avoid security anti-patterns. This guideline applies to test files that perform fuzz testing of crypto logic; implement a consistent seed setup (e.g., fixed seed in test initialization) and document the rationale to enable deterministic replays across runs.

Applied to files:

  • test/unit/docs/package-docs.test.js
  • test/unit/docs/release-truth.test.js
  • test/unit/docs/release-state.test.js
📚 Learning: 2026-03-30T19:53:48.000Z
Learnt from: flyingrobots
Repo: git-stunts/git-cas PR: 29
File: docs/design/TR-010-planning-index-consistency-review.md:121-131
Timestamp: 2026-03-30T19:53:48.000Z
Learning: In this repo, CHANGELOG.md entries should be user-facing and descriptive (bullet points) rather than cycle-ID headings (e.g., use a phrase like “Planning-index consistency review” instead of a “TR-010 — …” heading). When searching the changelog, don’t rely on grepping for cycle IDs (e.g., “TR-010”) because it may cause false negatives; search for the descriptive keywords/phrases from the bullet entries instead.

Applied to files:

  • CHANGELOG.md
🪛 Betterleaks (1.7.0)
docs/design/0055-internal-commit-identity/witness/release-publication.md

[high] 15-15: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

🪛 LanguageTool
docs/design/0057-deterministic-ref-conflict-posture/witness/release-candidate.md

[grammar] ~13-~13: Use a hyphen to join words.
Context: ...re-publication candidate for the Bijou 7 hosted cockpit and deterministic checked...

(QB_NEW_EN_HYPHEN)

🔇 Additional comments (26)
CHANGELOG.md (1)

10-11: LGTM!

README.md (2)

52-52: LGTM!


231-232: LGTM!

UPGRADING.md (1)

5-20: LGTM!

docs/releases/v6.5.6.md (1)

1-55: LGTM!

jsr.json (1)

3-3: LGTM!

package.json (2)

3-3: LGTM!


45-45: LGTM!

src/package-version.js (1)

1-1: LGTM!

test/unit/docs/release-state.test.js (7)

7-11: LGTM!


40-64: LGTM!


198-200: LGTM!


219-263: LGTM!


390-394: LGTM!


405-413: LGTM!


425-433: LGTM!

test/unit/docs/release-truth.test.js (1)

311-325: LGTM!

test/unit/docs/package-docs.test.js (1)

23-23: LGTM!

Also applies to: 100-100

BEARING.md (1)

22-27: LGTM!

Also applies to: 95-98, 154-165

ROADMAP.md (1)

46-46: LGTM!

Also applies to: 55-59

STATUS.md (1)

3-5: LGTM!

Also applies to: 21-33, 156-156

docs/design/0055-internal-commit-identity/witness/release-publication.md (1)

1-56: LGTM!

docs/design/0056-bijou-7-framed-cockpit/bijou-7-framed-cockpit.md (1)

10-10: LGTM!

Also applies to: 21-21, 321-321, 362-363, 374-379

docs/design/0057-deterministic-ref-conflict-posture/deterministic-ref-conflict-posture.md (1)

10-10: LGTM!

Also applies to: 21-21, 292-293, 340-347

docs/design/0057-deterministic-ref-conflict-posture/witness/release-candidate.md (1)

1-77: LGTM!

docs/design/README.md (1)

13-14: LGTM!

Also applies to: 47-48


📝 Walkthrough

Summary by CodeRabbit

  • New Features

    • Added the v6.5.6 release, featuring an interactive cockpit hosted through Bijou 7.2’s framed application boundary.
    • Added deterministic checked-reference conflict classification based on post-failure reference state.
  • Documentation

    • Added v6.5.6 release notes and upgrade guidance.
    • Updated release, roadmap, status, and design documentation to reflect the release candidate.
    • Documented that no public API or stored-data migration is required.
  • Chores

    • Updated package metadata and release links to version 6.5.6.

Walkthrough

v6.5.6 release-candidate metadata, documentation, design records, packaging, and release-state tests are updated. The release documents describe the hosted Bijou cockpit boundary and deterministic checked-ref conflict classification without public API or stored-data schema changes.

Changes

v6.5.6 Release Candidate

Layer / File(s) Summary
Release metadata and public documentation
CHANGELOG.md, README.md, UPGRADING.md, docs/releases/v6.5.6.md, package.json, jsr.json, src/package-version.js
Version references advance to v6.5.6, release notes and upgrade guidance are added, and the new release document is included in the package surface.
Release-cycle and design evidence
BEARING.md, ROADMAP.md, STATUS.md, docs/design/...
The framed cockpit and deterministic ref-conflict designs are marked landed, with candidate, publication, verification, and release-witness records updated.
Release-state validation
test/unit/docs/package-docs.test.js, test/unit/docs/release-state.test.js, test/unit/docs/release-truth.test.js
Tests validate packaged documentation, candidate-only publication evidence, historical release evidence, and v6.5.6 documentation contracts.

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

Possibly related PRs

Suggested reviewers: git-stunts

Poem

A rabbit hops through release notes bright,
Bijou frames the cockpit right.
Ref conflicts posture, clear and keen,
Candidate markers stay unseen.
Six-five-six now bounds the way!

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description omits all required template sections: linked issue, design/proof, validation block, and release impact checklist. Add the template sections with issue references, design/witness links, validation commands/results, and release-impact checklist items.
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title is concise and accurately summarizes the release version change and matches the main purpose of the PR.
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.
✨ Finishing Touches 💡 1
📝 Generate docstrings 💡
  • Create stacked PR
  • Commit on current branch

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@flyingrobots

Copy link
Copy Markdown
Member Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Jul 30, 2026

Copy link
Copy Markdown
✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@flyingrobots
flyingrobots merged commit 257e882 into main Jul 30, 2026
11 checks passed
@flyingrobots
flyingrobots deleted the release/v6.5.6 branch July 30, 2026 08:12
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.

1 participant