Repository navigation
chore(deps): bump hono from 4.12.14 to 4.12.16 in the npm_and_yarn group across 1 directory - #123
Merged
PatrickSys merged 104 commits intoOct 29, 2026
Merged
Conversation
Bumps the npm_and_yarn group with 1 update in the / directory: [hono](https://github.com/honojs/hono). Updates `hono` from 4.12.14 to 4.12.16 - [Release notes](https://github.com/honojs/hono/releases) - [Commits](honojs/hono@v4.12.14...v4.12.16) --- updated-dependencies: - dependency-name: hono dependency-version: 4.12.16 dependency-type: direct:production dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Contributor
|
No reviewable files after applying ignore patterns. |
The released branch was loading transformers 3.8.1 correctly, but the reranker was calling the tokenizer in a shape that ignored the passage. Keep the dependency on the released package version and make the recovery test assert the text_pair call so this does not slip back.
The repo is already on 2.3.0, but the release truth test and manual publish fallback were still pinned to 2.2.0. Derive the assertions from package metadata and normalize macOS temp paths so the full suite checks the real contract instead of local path spelling.
Move the local embedding and reranker integrations onto the stable v4 API and ONNX Runtime 1.24.3. This removes the macOS crash dependency while preserving the tokenizer pair fix already covered by this branch.
Remove secret-named variables before Vitest starts and suppress Node loader deprecations in the CLI subprocess contract. This keeps ContextBench fixtures free of operator environment values and preserves meaningful stderr assertions on Node 26.
chore(embeddings): upgrade Transformers.js to v4
test: keep scoped memory fixtures fresh
React 19 and Next 16 added framework signals that the analyzers were not classifying yet. Keep the analyzer surface current without touching core search or indexing behavior.
We work in NestJS code often enough that treating it as generic TypeScript loses useful context. Add a dedicated analyzer for controllers, modules, providers, routes, DI, and common Nest packages so backend code gets the same first-class treatment as React and Next.js.
Large repositories were silently limited to the first 5,000 searchable chunks. Let each configured project raise that safety limit while keeping 5,000 as the default for smaller codebases. Use the same setting in MCP server and CLI reindex paths so both keyword and semantic indexes cover the same files.
Keep the auto-extracted Git history in project memory so future searches can surface the fixes and test constraints already handled in this repository.
NestJS imports are a stronger framework signal than Angular's shared decorator names. Give the NestJS analyzer precedence so providers keep their Nest-specific classification and metadata.
A function named use is not necessarily React's API. Track the actual React import binding so local and unrelated use calls do not add hook or Suspense metadata.
feat(analyzers): recognize NestJS projects
Add the first public review-context vertical slice to codebase-context: exact committed diff envelopes, bounded deterministic change signals, repository retrieval, versioned review-context-v1 output, runtime tests, documentation, and the autonomous product spec/roadmap. No reviewer-quality claims are made; the next gate is a frozen public evaluation.
Record the completed functional publishability gate, evidence level E1, and Phase 1 as the active benchmark-freeze work.
* docs: publish benchmark evidence and released setup guidance * fix(docs): preserve package links and evidence contracts
* fix(search): clarify first-use indexing guidance * fix(search): clarify index retry guidance * fix: require Node 22 and test supported LTS versions
* fix: route help to CLI usage * test: keep the original help response timeout
* docs: align 2.4.0 release guidance * fix: align release workflow with 2.4.0 * docs: explain real setup and 2.4.0 changes * fix(release): require an explicit manual publish tag * docs: qualify unreleased version commands across guides * Fix 2.4.0 setup notices
* docs: use published npm install commands * docs: keep 2.2.0 analyzers current and mark 2.4.0-only commands Addresses Codex/Greptile review on #141: Angular/React/Next.js analyzers ship in 2.2.0 (only NestJS is upcoming); init --client/--yes, codebase-context-review and parsing.maxChunks require unpublished 2.4.0, so those commands are pinned and labelled. Release-truth test allows 2.4.0 pins only next to a 'requires 2.4.0' note.
Default Windows test files to one worker through the existing Vitest configuration. Explicit worker flags still override the default. The full Windows suite passes with its existing assertions and timeouts. Agent-Harness: codex Agent-Session: J62-cbc-night-20261029-28964
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 32715605 | Triggered | Generic High Entropy Secret | d6414b3 | .github/workflows/contextbench-real-gpt54mini-auth-one.yml | View secret |
| 32715643 | Triggered | Generic High Entropy Secret | 3cbb64b | .github/workflows/contextbench-real-gpt54mini-auth-vars-one.yml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
dependabot
Bot
deleted the
dependabot/npm_and_yarn/npm_and_yarn-03cc7c73db
branch
October 29, 2026 19:53
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the npm_and_yarn group with 1 update in the / directory: hono.
Updates
honofrom 4.12.14 to 4.12.16Release notes
Sourced from hono's releases.
Commits
90d41824.12.16db05b96Merge commit from fork614b834Merge commit from fork027e3dffix(method-override): handle Content-Type with charset parameter (#4894)f774f8d4.12.1518fe604fix(jwt): support single-line PEM keys (#4889)You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.