chore(deps): bump next from 14.2.35 to 16.1.6 in /.agents/skills/ai-sdk-ui/templates in the npm_and_yarn group across 1 directory#1
Closed
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the npm_and_yarn group with 1 update in the /.agents/skills/ai-sdk-ui/templates directory: [next](https://github.com/vercel/next.js). Updates `next` from 14.2.35 to 16.1.6 - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v14.2.35...v16.1.6) --- updated-dependencies: - dependency-name: next dependency-version: 16.1.6 dependency-type: direct:production dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
✅ Deploy Preview for protocol-guide ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
Author
|
Looks like next is no longer a dependency, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/dot-agents/skills/ai-sdk-ui/templates/npm_and_yarn-cc9e6c862d
branch
thefiredev-cloud
pushed a commit
that referenced
this pull request
Feb 24, 2026
- Split 531-line relations.ts into 5 focused modules - Created drizzle/relations/ directory with: - user-relations.ts (281 lines) - User, county, auth, bookmark relations - agency-relations.ts (67 lines) - Agency, member, invitation relations - protocol-relations.ts (76 lines) - Protocol chunk, version, upload relations - analytics-relations.ts (100 lines) - Analytics and query feedback relations - supabase-relations.ts (22 lines) - Manus production table relations - Original relations.ts now barrel exports from ./relations/index - All files under 500-line limit - TypeScript compilation passes (pnpm check) Sprint 20 refactoring - Split #1 of 5
thefiredev-cloud
pushed a commit
that referenced
this pull request
Apr 15, 2026
…om Appendix K Enables /pg-rag-audit skill to run. Entries cover the emergent categories ($critical severity) where silent drift would be highest- impact: pediatric dosing (3), emergent cardiac (3), contraindication (1), adult dosing (2), airway/RSI (1), stroke (2), sepsis (1), abbreviation (1). Source discipline per Appendix K: - NHTSA National EMS Education Standards 2021 (public domain) - NYS DOH Statewide BLS Protocols v25.1 - AHA 2025 ACLS + PALS (Circulation — paraphrase algorithm logic, never copy figures verbatim) - California EMSA Scope of Practice 2024 - PMC / WikEM / EMCrit / LITFL / EMRA (attribute, paraphrase) - Explicitly NOT: NREMT packet text, J&B PHTLS/AMLS/EPC chapters, commercial question banks (all copyrighted). Each entry schema: id, query, category, severity, expectedKeyterms, mustCiteProtocol, baselineAnswer, frozen, reviewedBy, reviewedDate, source. `frozen: false` on every entry — clinical review is a pre-requisite for any entry to gate deployment. Target path to v1: - Week 1: Draft 200 entries from public sources (~25-30 hrs) - Week 2: Paramedic SME pass #1 — flag dosing disputes - Week 3: EMS physician sign-off on all critical + pediatric - Week 4: Pilot regression vs live app, baseline metrics Until then, /pg-rag-audit runs advisory-only on these 15 (no `frozen`-gate blocks a ship).
thefiredev-cloud
pushed a commit
that referenced
this pull request
Apr 24, 2026
Tools tab was `href: null` — all 20+ clinical agents (handoff, ePCR, walker, differential, radio-report, etc.), plus the newly-shipped Demo Mode and flag-gated Full Call Workflow, were orphaned. Users saw only Protocols + Profile, no path to the product's headline clinical features. Fix: promote Tools from hidden to visible. Order: Protocols / Tools / Profile. Other hidden routes (settings/search/calculator/coverage/ history) stay hidden — they're accessed from inline nav, not the tab bar. Unblocks: App Store reviewer seeing full product value, Christian testing AI agents, anonymous prospects reaching Demo Mode. Per docs/superpowers/specs/2026-04-24-build43-ux-blockers-design.md #1.
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 /.agents/skills/ai-sdk-ui/templates directory: next.
Updates
nextfrom 14.2.35 to 16.1.6Release notes
Sourced from next's releases.
... (truncated)
Commits
adf8c61v16.1.6098c0c0[backport][ci] Make gh auth status optional when triggering a release (#89100)a43df32Backport/docs fixes jan 25 16.1.x (#89124)d6d5734tweak LRU sentinel cache key (#89123)4324698backport: implement LRU cache with invocation ID scoping for minimal mode res...23c4649[backport] Upgrade to swc 54 (#88207) (#89103)acba4a6v16.1.5e1d1fc6Add maximum size limit for postponed body parsing (#88175)500ec83fetch(next/image): reduce maximumResponseBody from 300MB to 50MB (#88588)1caaca3feat(next/image)!: addimages.maximumResponseBodyconfig (#88183)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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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.