Skip to content

Conversation

@Themezv
Copy link
Member

@Themezv Themezv commented Dec 21, 2025

Note

Migrates the monorepo to pnpm and aligns build, CI, and deployment pipelines.

  • Replace Yarn with pnpm in all Dockerfiles (corepack enable, cached pnpm install, pnpm next build, pnpm deploy), adjust runtime ENTRYPOINTS and copy .next/static
  • Add pnpm workspace config: new .npmrc (engine, hoist), pnpm-workspace.yaml with shared catalog, update package.json engines/scripts
  • Update GitHub Actions to use pnpm (pnpm/action-setup, pnpm cache, pnpm scripts) and watch pnpm-lock.yaml; expand deploy branches to include pnpm
  • Revise Ligretto CI/CD: add artifacted frontend build, Buildx caching scopes, and Helm-based deploy steps for core/gameplay backends and S3 frontend deploy; add scheduled/PR E2E workflow
  • Clean up ignores and configs (.gitignore, .eslintignore, VSCode settings), README instructions switched to pnpm install

Written by Cursor Bugbot for commit aa8c739. This will update automatically on new commits. Configure here.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

steps:
- uses: actions/checkout@main
name: Checkout

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deploy jobs removed without replacement, breaking deployments

The deploy job now only checks out the repository but performs no actual deployment. The deploy-to-swarm action was removed but not replaced with an alternative deployment mechanism. When code is merged to master, the deploy job will complete successfully without deploying anything to production.

Additional Locations (1)

Fix in Cursor Fix in Web

- packages/*
- apps/*
catalog:
"@adonisjs/assembler": ^5.7.0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

А разве это не зависимость только одного сервиса?

@Themezv Themezv had a problem deploying to Ligretto-production January 11, 2026 21:14 — with GitHub Actions Failure
@Themezv Themezv had a problem deploying to Ligretto-production January 11, 2026 21:14 — with GitHub Actions Failure
@Themezv Themezv had a problem deploying to Ligretto-production January 11, 2026 21:15 — with GitHub Actions Failure
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

steps:
- uses: actions/checkout@main
name: Checkout

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deploy jobs removed, workflows do nothing

High Severity

The deploy jobs in both blog-deploy.yml and gamehub-deploy.yml had their deployment steps completely removed. The jobs now only perform a checkout without any actual deployment action. When these workflows run, they will appear to succeed but won't deploy anything to production. The deploy-to-swarm action calls were removed without replacement, leaving the deploy jobs empty.

Additional Locations (1)

Fix in Cursor Fix in Web


on:
pull_request:
branches: [ pnpm ]
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR trigger accidentally added to scheduled workflow

Low Severity

A pull_request trigger for the pnpm branch was added to the ligretto-schedule-e2e.yml workflow. This workflow is meant to run on a schedule (daily cron) and manual dispatch, not on pull requests. This appears to be temporary testing code that was accidentally included and will remain after the PR is merged.

Fix in Cursor Fix in Web

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.

3 participants