TIG-254: Move tagger into backend#3
Open
yubimamiya wants to merge 19 commits into
Open
Conversation
Bumps [urllib3](https://github.com/urllib3/urllib3) from 2.6.3 to 2.7.0. - [Release notes](https://github.com/urllib3/urllib3/releases) - [Changelog](https://github.com/urllib3/urllib3/blob/main/CHANGES.rst) - [Commits](urllib3/urllib3@2.6.3...2.7.0) --- updated-dependencies: - dependency-name: urllib3 dependency-version: 2.7.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
… routes - New root README.md focused on getting apps/web running (replaces stale SETUP.md) - Fix DATABASE_URL port 5432 -> 5434 in package .env examples to match docker-compose - Complete apps/web/.env.local.example with all vars required by src/env.ts - Remove old /5 /6 /7 /8 design-mockup routes from apps/web - Add CI guard: PRs into main must come from staging
docs: developer setup README + env example fixes + remove old mockup routes
Release: developer setup README, env fixes, mockup route cleanup
…i/urllib3-2.7.0 chore(deps): bump urllib3 from 2.6.3 to 2.7.0 in /backends/fastapi
- Bump pyasn1, cryptography, pygments, idna, starlette, requests, pytest, python-dotenv in backends/fastapi (covers Dependabot PRs #2-#8, #10, which conflicted on uv.lock after #1 merged) - Bump drizzle-orm ^0.38.3 -> ^0.45.2 (high-severity alert, no Dependabot PR existed for the bun lockfile) + drizzle-kit ^0.30.4 -> ^0.31.10 Verified: FastAPI app imports and serves on starlette 1.2.1; web app typechecks and production-builds; drizzle runs queries against live Postgres.
fix(security): resolve all 12 Dependabot alerts + README polish
Release: resolve all Dependabot vulnerabilities + setup docs polish
- Skip events whose title already exists — re-running db:seed no longer duplicates all 21 demo events (events have no unique constraint to lean on for onConflictDoNothing) - Seed user_regions (set during onboarding, previously empty) - Add a pending friend request + matching friend_request notification, plus org_new_event and event_reminder notifications with payload shapes mirroring apps/web server actions - Seed interactions (implicit feedback) from the generated RSVPs/saves plus views/clicks, using the same weights as logInteraction, so the recommendation pipeline has data to work with - Notifications/interactions have no natural unique key, so they are only seeded into an empty table Tested: ran twice against a scratch database — second run is a no-op (21 events, 3 notifications, 177 interactions, no duplicates).
feat(seed): make re-runnable and cover newer tables
Release: re-runnable seed with newer-table coverage
# Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
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
4 participants
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.
Technical Documentation: https://docs.google.com/document/d/1OGwtYvPLSNfOmgwFi0mSn0AWvuWeSvUu1-j1I0XKq00/edit?usp=sharing