Skip to content

chore(deps): bump lucide-react from 0.294.0 to 1.8.0 in /tap-dashboard#5

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/tap-dashboard/lucide-react-1.8.0
Open

chore(deps): bump lucide-react from 0.294.0 to 1.8.0 in /tap-dashboard#5
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/tap-dashboard/lucide-react-1.8.0

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot Bot commented on behalf of github Apr 13, 2026

Bumps lucide-react from 0.294.0 to 1.8.0.

Release notes

Sourced from lucide-react's releases.

Version 1.8.0

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.7.0...1.8.0

Version 1.7.0

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.6.0...1.7.0

Version 1.6.0

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.5.0...1.6.0

Version 1.5.0

What's Changed

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for lucide-react since your current version.


Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot @github
Copy link
Copy Markdown
Author

dependabot Bot commented on behalf of github Apr 13, 2026

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Apr 13, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
molt.os Ready Ready Preview, Comment Apr 22, 2026 5:39pm

Request Review

@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/tap-dashboard/lucide-react-1.8.0 branch from 96ba40f to 3216853 Compare April 13, 2026 21:59
Shepherd217 pushed a commit that referenced this pull request Apr 17, 2026
- POST /api/agent/hospital/intake/[id]/self-discharge
  Solo agents can close their own self-admitted intakes without needing
  an external specialist. Earns +1 TAP, logs positive dreaming entry.
  Blocks: must be patient, must be self-admitted.

- /api/agent/acquire: warn acquirer if skills_wanted won't transfer
  New fields in response: target_skills_available, skills_missing_on_target,
  warning (if all skills missing) or notice (if partial miss).
  Prevents silent offer submissions that expire with nothing to transfer.

Unblocks Promachos unlock sequence: Hospital proof #5, M&A clarity.
Bumps [lucide-react](https://github.com/lucide-icons/lucide/tree/HEAD/packages/lucide-react) from 0.294.0 to 1.8.0.
- [Release notes](https://github.com/lucide-icons/lucide/releases)
- [Commits](https://github.com/lucide-icons/lucide/commits/1.8.0/packages/lucide-react)

---
updated-dependencies:
- dependency-name: lucide-react
  dependency-version: 1.8.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/tap-dashboard/lucide-react-1.8.0 branch from 3216853 to 7c0887f Compare April 22, 2026 17:38
Shepherd217 added a commit that referenced this pull request May 26, 2026
#5)

Pre-fix, any agent with sufficient reputation could file disputes against phantom target_ids, polluting dispute_cases and wasting committee cycles. Now validates target exists in agent_registry (agent), attestations (attestation), or agent_vouches (vouch) BEFORE the bond lock fires. Returns 404 TARGET_NOT_FOUND on miss. tsc clean. See REDTEAM-ADVERSARIAL-2026-05-22.md for the full probe results.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Shepherd217 added a commit that referenced this pull request May 26, 2026
…agent_registry select

The home route was selecting an agent_registry row without trajectory_grade or
violation_count, then passing it to computeNextAction(). The trajectory_advisor
gate at lib/next-action.ts:134 relies on agentRow.trajectory_grade being
populated to suppress a competing completion_rate calculation when the canonical
trajectory scorer has already given the agent grade A/B/C.

With trajectory_grade undefined, the gate never fired. Promachos (Grade B,
job_completion_rate 0.684 per /api/agent/trajectory) received a next_action
telling him his completion rate was 25% and below the Grade-C threshold, while
/api/agent/trajectory simultaneously reported him as Grade B.

Same agent, one truth. Surgical: select two more columns; no logic changes.

Verified against DAYINLIFE-2026-05-22.md Friction #5 and RETEST-PROMACHOS-2026-05-22.md
checkpoint 3.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.

0 participants