You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[shared-ci] test failing across projectbluefin/website #1025
Summary: The test check is failing on 4 open pull requests in projectbluefin/website at the same time. When one check fails on this many pull requests, the cause is usually shared (the base branch, a workflow, a pinned action or the runner image), not any single change. The hive opened this issue so the failure is looked at once, here, instead of once per pull request.
Default branch: the newest run of this check on the base branch is not red. Either these pull requests are behind their base, or something outside the branch changed since that run (a moved action tag, a new runner image, an upstream outage).
Log excerpt from the failing runs:
Process completed with exit code 1.
'flipViewport' is declared but its value is never read.
Missing JSDoc returns description
Arrays with 4 or more items on a line longer than 40 should have line breaks between items
Complex ternaries should have line breaks before `:`
Complex ternaries should have line breaks before `?`
Items containing calls, functions, ternaries, complex spreads or non-empty nested objects/arrays should have line breaks between items
Next step
Repair the shared cause once, usually with one pull request against the base branch or the shared workflow, then close this issue. Pull requests that are only behind their base may also need their branch updated.
The hive keeps this description in step with the failing pull requests while the failure lasts (edits do not notify) and does not comment on the pull requests listed here.
Good first issue — withdrawn by hosted-projectbluefin-knuckle-gjvq: this issue is not open to new contributors — it is waiting on a person (stage/045-needs-decision). The good first issue and help wanted labels have been removed (2026-11-16T19:09:52Z). Sorry for the noise! Issues open to new contributors are listed on the relay page: https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute
The [shared-ci] tracker #1025 is not a single shared-infra break — it is four independent renovate dependency bumps, each failing for its own reason. This repo is still green because it runs the old dependency versions; each PR bumps a dep and surfaces a latent incompatibility that the old versions hid.
What I need from you: the fixes live on the upstream renovate branches, which a bot without push access cannot edit, so each branch needs its author or a maintainer to address it individually.
newer antfu rules (e.g. reasonable-newline) now fire on existing code
Run eslint --fix on the branch
Why there is no single shared fix. The report's guess ("usually shared — base branch, a workflow, a pinned action, or the runner image") does not hold here. Each PR fails for a different reason, and the base branch passes because it still uses the old deps. Regenerating the base lockfile or editing base code would touch neither these branches' own dependency versions nor their own lockfiles, so it would not unblock any of them.
I confirmed each item by reading the failing PR's CI run and its step conclusions. As a control, this repo's own package-lock.json is fully consistent with package.json, so a stale-lockfile-on-main angle is ruled out.
Closing: there was no shared cause. As kylerankin's table above shows, each PR fails for its own reason, and main is green. Each has its own fix issue now:
Activity
hivecommons-hive commentedon Nov 16, 2026
Good first issue— withdrawn by hosted-projectbluefin-knuckle-gjvq: this issue is not open to new contributors — it is waiting on a person (stage/045-needs-decision). Thegood first issueandhelp wantedlabels have been removed (2026-11-16T19:09:52Z). Sorry for the noise! Issues open to new contributors are listed on the relay page: https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contributekylerankin commentedon Nov 16, 2026
The [shared-ci] tracker #1025 is not a single shared-infra break — it is four independent renovate dependency bumps, each failing for its own reason. This repo is still green because it runs the old dependency versions; each PR bumps a dep and surfaces a latent incompatibility that the old versions hid.
What I need from you: the fixes live on the upstream renovate branches, which a bot without push access cannot edit, so each branch needs its author or a maintainer to address it individually.
npm cipackage-lock.jsonis out of sync withpackage.json(the PR is package.json-only)npm cipackage-lock.jsonis out of sync withpackage.json(the PR is package.json-only)npm run typecheckflipViewportis declared but never read; the newer typecheck flags it as unusednpm run lintreasonable-newline) now fire on existing codeeslint --fixon the branchWhy there is no single shared fix. The report's guess ("usually shared — base branch, a workflow, a pinned action, or the runner image") does not hold here. Each PR fails for a different reason, and the base branch passes because it still uses the old deps. Regenerating the base lockfile or editing base code would touch neither these branches' own dependency versions nor their own lockfiles, so it would not unblock any of them.
I confirmed each item by reading the failing PR's CI run and its step conclusions. As a control, this repo's own
package-lock.jsonis fully consistent withpackage.json, so a stale-lockfile-on-main angle is ruled out.— hive: backend=pi model=lemonade/ornith-1.5-35b-a3b-gguf-q6_k
🐝 Hive Agent:
contributor| SHA:a8f57cadDanathar commentedon Nov 17, 2026
Closing: there was no shared cause. As kylerankin's table above shows, each PR fails for its own reason, and
mainis green. Each has its own fix issue now:flipViewportref. See fix: remove unused flipViewport ref so vue-tsc 3.3.14 passes #1032.