Skip to content

Dev to main merge - #1182

Merged
prakashchoudhary07 merged 10 commits into
mainfrom
develop
Oct 4, 2026
Merged

prakashchoudhary07 merged 10 commits into
mainfrom
develop

Conversation

@prakashchoudhary07

@prakashchoudhary07 prakashchoudhary07 commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

Date: 05-10-26

Developer Name: @geekyvaishnavi


Issue Ticket Number:-

PRs going for Sync-

Description:

  • Show event ID in an (i) info card on the live page after joining
  • Refactor new join steps to use username for social steps, add dribbble and replace company with college
  • Add tests for new join steps
  • Fix status card for request changes and application redirection
  • Upgrade 100ms video store and pin pnpm 12

Is Under Feature Flag

  • Yes
  • No

Database changes

  • Yes
  • No

Breaking changes (If your feature is breaking/missing something please mention pending tickets)

  • Yes
  • No

Is Development Tested?

  • Yes
  • No

Tested in staging?

  • Yes
  • No

Add relevant Screenshot below ( e.g test coverage etc. )

staging proofs

  1. Show event ID in info card on live page after joining (feat: show event ID in info card on live page after joining #1179)
Screenshot 2026-10-05 at 2 41 37 AM Screenshot 2026-10-05 at 1 40 43 AM

MayankBansal12 and others added 10 commits March 24, 2026 02:12
* fix: status card for changes requested and application redirection

* test: fix breaking test for application detail
* fix: status card for changes requested and application redirection

* test: fix breaking test for application detail

* test: new join step one, two, three
* chore: migrate to pnpm 11 with devEngines-managed node runtime

pnpm 11 stopped reading settings from .npmrc, which silently dropped the
hoisting config the Ember build relies on, and its strict build-script
policy fails installs until dependencies are reviewed. Move settings to
pnpm-workspace.yaml with an explicit allowBuilds policy, and replace the
advisory volta pin with devEngines (onFail: download) so pnpm itself
provisions the exact node and pnpm versions from the lockfile.

Co-authored-by: Cursor <cursoragent@cursor.com>

* ci: let pnpm provision node via devEngines, pin pnpm major, cache store

setup-node and the node matrix are redundant now that pnpm downloads the
lockfile-pinned runtime itself. Pin pnpm/action-setup to major 11 instead
of "latest" (which is what broke CI when pnpm 11 shipped); the precise
version stays governed by devEngines. Also add pnpm store caching and
bump checkout off deprecated v2/v3.

Co-authored-by: Cursor <cursoragent@cursor.com>

* chore: drop only-allow preinstall guard

devEngines.packageManager now pins pnpm itself, and the committed
pnpm-lock.yaml makes npm/yarn installs fail naturally, so the guard is
redundant.

Co-authored-by: Cursor <cursoragent@cursor.com>

* ci: pin action refs to commit SHAs

Tags are mutable, so a compromised action repository could repoint them
at malicious code. Pinning to full commit SHAs (with the tag noted in a
comment) keeps the executed workflow code fixed.

Co-authored-by: Cursor <cursoragent@cursor.com>

* docs: document refreshing pinned action SHAs

SHA pins do not update themselves, so record why they exist and the
procedure for bumping them in README, with a pointer from the workflow.

Co-authored-by: Cursor <cursoragent@cursor.com>

* fix: bootstrap pnpm standalone and restore engineStrict (review feedback)

pnpm 11 needs Node >= 22.13 just to start (node:sqlite), so an
npm/Corepack-installed pnpm on an older Node crashes before
devEngines.runtime can download the pinned Node. Install pnpm standalone
in CI (@pnpm/exe bundles its own Node) and document the standalone
install script for contributors. Also carry engine-strict=true from the
deleted .npmrc into pnpm-workspace.yaml as engineStrict.

Co-authored-by: Cursor <cursoragent@cursor.com>

* fix: keep eslint out of local agent worktrees under .claude/

The '!**/.*' ignore negation (needed to lint dotfiles like .prettierrc.js)
also un-ignored .claude/, so eslint walked the agent worktree checkouts and
failed no-undef on their copies of root-relative CJS files. Re-ignore
.claude/ after the negation, since the last matching pattern wins.

Co-authored-by: Cursor <cursoragent@cursor.com>

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
…replace company with college (#1159)

* refactor: new join steps and social steps to use profile username

* fix: naming and bg color for social pill

* refactor: new step four to use config

* fix: safely normalize social profile usernames
* refactor: new join steps and social steps to use profile username

* fix: naming and bg color for social pill

* refactor: new step four to use config

* fix: safely normalize social profile usernames

* test: add tests for new join steps 4 and 5

* test: add test for new join step four

* fix: assertion for step six for empty values

* test: cover social username normalization
devEngines pinned pnpm to the 11.x major, so anyone whose installed pnpm is
12 (the current latest) paid a provisioning hop on every command: pnpm
resolved the pin, downloaded pnpm 11 into its version store, and re-executed
through it. That measured roughly 1.4s per command against 0.01s once the
pin matches the installed major.

pnpm 12 is also a native executable with no Node.js launcher, so it avoids
the pnpm 11 failure mode where the native binary is only linked once a build
script runs and pnpm quietly falls back to Node when that build is skipped.

Update the CI workflow pins and the README prerequisite to match, and
rewrite the README rationale for avoiding npm and Corepack installs, which
no longer turns on pnpm 11's Node >= 22.13 bootstrap requirement.

Verified on a clean install: pnpm install, pnpm build and pnpm test all exit
0, with 408 tests (402 passed, 6 skipped, 0 failed) and every lint job
green. The lockfile change is confined to the pnpm provisioning entries, so
no application dependency changes version.

Closes #1173


Claude-Session: https://claude.ai/code/session_01CYgJmq2cxggmE8TGGiFDRi

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* chore: upgrade @100mslive/hms-video-store to 0.14.7

Bumps the 100ms SDK used by the live events page from 0.10.6 (2023) to
0.14.7. Since 0.11 the core @100mslive/hms-video package is bundled into
hms-video-store, so it drops out of the lockfile.

The only code change is a guard in LiveService.renderScreenVideoToPeers:
detachVideo now reads the SDK store, which only exists after a room has
been joined, and the peers subscription fires on construction. Without
the guard the service throws (unhandled rejection) on every page that
injects it before join.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* chore: upgrade @100mslive/hms-video-store to 0.15.0

Entire-Checkpoint: 01M27X1H3G7V7Y686T8BT20V5Q

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
* feat: show event ID in info card on live page after joining

* fix: show event ID card on keyboard focus

* fix: improve event info card accessibility and close on Escape

* fix: allow reopening event info card via click/Enter after Escape
@coderabbitai

coderabbitai Bot commented Oct 4, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 313ed695-c086-4ee2-ad3d-15458bcc1794

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@prakashchoudhary07

Copy link
Copy Markdown
Contributor Author

Approved the PR and merged it
Since the person who raised the PR and the reviewer are the same, they cannot approve it there, so I will merge it

@prakashchoudhary07
prakashchoudhary07 merged commit 80eee34 into main Oct 4, 2026
4 checks passed
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.

4 participants