Uh oh!
There was an error while loading. Please reload this page.
chore(deps): bump hono from 4.11.9 to 4.11.10 - #699
Merged
Conversation
Bumps [hono](https://github.com/honojs/hono) from 4.11.9 to 4.11.10. - [Release notes](https://github.com/honojs/hono/releases) - [Commits](honojs/hono@v4.11.9...v4.11.10) --- updated-dependencies: - dependency-name: hono dependency-version: 4.11.10 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
ContributorAuthor
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Uh oh!
There was an error while loading. Please reload this page.
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
os-zhuang pushed a commit
that referenced
this pull request
Aug 23, 2026
…e the pin (#5442) ⛔ Comments only. This commit is a NO-OP to the workflow's execution: the pinned version, every input, every `if:` and every step body are byte-identical, and `yaml.safe_load` of the file before and after parses to structurally identical objects. Verified mechanically, not by eye. Dependabot proposed changesets/action v1 -> v2 in both repositories and it was declined in both — objectstack#9208 (closed unmerged 2026-08-19) and objectui#4945 (closed unmerged 2026-08-23). objectstack recorded the reasoning in its own repo (objectstack#9916); objectui had no equivalent, and #5442 makes that urgent: before it the pin rested on one v1 property, after it on two. The block states why v1 is pinned (safety properties asserted against v1's source, not a version preference), the two properties an upgrade must re-verify — the `!hasChangesets && hasPublishScript -> runPublish` dispatch table, and that `runPublish` never commits and never pushes a branch — and the five v2 changes readable from its CHANGELOG that would break this file. The second property is the sharp one: it is what makes the clear step's runner-local deletion safe, and v2's #692 moves pushes to the GitHub API by default, which is a different code path than the one that verification covers. It also records the plausible wrong answer explicitly: the Changesets CLI generation is NOT what pins us. v2's #699 directs CLI v2 users to @v1, and this repository is on CLI v3 (`^3.0.0`, lockfile 3.0.1). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0124Qg8rLvpXnQDwCmpKUmaJ
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 freeto 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 hono from 4.11.9 to 4.11.10.
Release notes
Sourced from hono's releases.
Commits
a40d2104.11.1091def7cMerge commit from fork8b17935test(types): add regression tests for #4388 (routes before .use() with explic...4a03f4fdoc(jwt): markoptions.secretas required in JSDoc (#4718)7300551chore(ci): bump typescript-go to the latest (#4716)4b29780chore: update Zod import examples to use namespace imports (#4715)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.