fixing - #292
Conversation
Bumps [react](https://github.com/facebook/react/tree/HEAD/packages/react) and [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react). These dependencies needed to be updated together. Updates `react` from 19.0.0 to 19.2.7 - [Release notes](https://github.com/facebook/react/releases) - [Changelog](https://github.com/react/react/blob/main/CHANGELOG.md) - [Commits](https://github.com/facebook/react/commits/v19.2.7/packages/react) Updates `@types/react` from 19.1.3 to 19.2.17 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react) --- updated-dependencies: - dependency-name: react dependency-version: 19.2.7 dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: "@types/react" dependency-version: 19.2.17 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
…ulti-b0dfc253ff Bump react and @types/react
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
There was a problem hiding this comment.
CodeQL found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.
|
Too many files changed for review. ( Bypass the limit by tagging |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_281e8d23-7f27-4946-99e3-d23e0cf7dacd) |
|
Visit the preview URL for this PR (updated for commit 63bb8e5): https://hacklytics2027--pr-292-tfs6x1tk.web.app (expires Sat, 08 Aug 2026 00:41:15 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: c48ba34db61581e25fe2978355160b5eefe0e83f |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_68156949-628b-481d-91c5-1a21b5f2badb) |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_ae56aecb-4128-4f91-8cc1-d22dd03e65f0) |
| FaFire, FaMapMarkedAlt, FaBrain, | ||
| FaRobot, FaPlay, FaVolumeUp | ||
| } from "react-icons/fa"; | ||
| import { FiCheckCircle, FiLock, FiAward } from "react-icons/fi"; |
| }; | ||
|
|
||
| // Achievements Definition | ||
| const achievements: Achievement[] = useMemo(() => [ |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_e1612e88-9e97-483b-a084-ba4a97d3c8c8) |
github-actions
Bot
added
the
dependencies
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 0c7adbf. Configure here.
| push: | ||
| branches: | ||
| - main | ||
| pull_request: |
There was a problem hiding this comment.
Duplicate Firebase deploy workflows
Medium Severity
Adding deploy-hacklytics.yml creates duplicate Firebase Hosting deployments for the hacklytics target. Existing workflows still run, causing main pushes to trigger two live deploys and PRs to trigger two preview deploys, which doubles CI work, checks, and PR comments.
Reviewed by Cursor Bugbot for commit 0c7adbf. Configure here.
|
|
||
| jobs: | ||
| build_and_deploy: | ||
| runs-on: ubuntu-latest |
There was a problem hiding this comment.
Missing fork guard on deploy
Medium Severity
The deploy-hacklytics.yml workflow runs on pull_request events from forks without checking if the PR head is from the same repository. This causes the job to execute and fail for fork PRs, as the FIREBASE_SERVICE_ACCOUNT_DSGT_WEBSITE secret is unavailable.
Reviewed by Cursor Bugbot for commit 0c7adbf. Configure here.
2 participants
Note
Medium Risk
Firebase workflow changes alter what gets built and deployed to production hosting; incorrect filter or entryPoint could break or mis-deploy the Hacklytics site, though scope is narrower than a full turbo build.
Overview
This PR retargets Firebase Hosting automation so CI builds and deploys only the Hacklytics 2027 site (
pnpm turbo run build --filter=hacklytics2027) instead of the full monorepo build, and setsentryPoint: "."on the Firebase deploy action so hosting config resolves from the repo root. Node in those workflows is pinned to 22.23.1; PR previews get an explicitchannelId(pr-{number}orlive).A new workflow
deploy-hacklytics.ymlmirrors merge/PR Firebase deploy behavior for pushes tomainand all pull requests.Graphify support is added via
.graphifyignore(whitelist code extensions) and.gitignoreentries forgraphify-out/cache/andgraphify-out/cost.json. The diff also addsgraphify-out/report artifacts (e.g.GRAPH_REPORT.md, labels, manifest).Remaining changes are formatting-only across GitHub issue templates, labeler YAML, CodeQL workflow indentation, and
.vscode/settings.json; minor whitespace inGCP_SETUP.mdand trailing newline onfirebase.json.Reviewed by Cursor Bugbot for commit 63bb8e5. Bugbot is set up for automated code reviews on this repo. Configure here.