Skip to content

[shared-ci] test failing across projectbluefin/website #1025

Closed

Description

@hivecommons-hive

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.

Evidence

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.

Activity

  1. added
    agent/ci-maintainerFiled or owned by the ci-maintainer agent.
    kind/bugCreated by Hive for agent-filed issue provenance
    origin/governorFiled by the Hive governor/automation on its own behalf (provenance only, not routing or hold)
    stage/010-actionableTriaged; eligible for the hive to pick up
    on Nov 16, 2026
  2. hivecommons-hive commented on Nov 16, 2026

    @hivecommons-hive
    ContributorAuthor

    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

  3. kylerankin commented on Nov 16, 2026

    @kylerankin
    Contributor

    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.


    PR Dependency bump Failing CI step Root cause Recommended fix
    #1009 tailwindcss 4.3.2 → 4.3.5 npm ci package-lock.json is out of sync with package.json (the PR is package.json-only) Regenerate the lockfile on the branch
    #1024 eslint (monorepo) npm ci package-lock.json is out of sync with package.json (the PR is package.json-only) Regenerate the lockfile on the branch
    #1019 vue-tsc 3.1.3 → 3.3.14 npm run typecheck flipViewport is declared but never read; the newer typecheck flags it as unused Remove the unused ref on the branch
    #1023 @antfu/eslint-config 6 → 10 npm run lint 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.

    — hive: backend=pi model=lemonade/ornith-1.5-35b-a3b-gguf-q6_k


    🐝 Hive Agent: contributor | SHA: a8f57cad

  4. added
    stage/045-needs-decisionIssue parked on a person: needs-human or a maintainer decision is owed before the hive picks it up
    and removed
    stage/010-actionableTriaged; eligible for the hive to pick up
    help wantedExtra attention is needed
    on Nov 16, 2026
  5. removed
    stage/045-needs-decisionIssue parked on a person: needs-human or a maintainer decision is owed before the hive picks it up
    on Nov 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent/ci-maintainerFiled or owned by the ci-maintainer agent.kind/bugCreated by Hive for agent-filed issue provenanceorigin/governorFiled by the Hive governor/automation on its own behalf (provenance only, not routing or hold)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions