Skip to content

chore: Prepare Writebook for Sentry's onboarding evals - #1

Open
sentry-junior[bot] wants to merge 1 commit into
mainfrom
sentry-evals
Open

sentry-junior[bot] wants to merge 1 commit into
mainfrom
sentry-evals

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Nov 7, 2026

Copy link
Copy Markdown

This fork is the Rails fixture for the sentry-ruby onboarding evals in getsentry/sentry-for-ai-evals, pinned there by commit sha.

  • Development Action Cable uses async instead of Redis, so the app starts in the eval container, which has no Redis server.
  • Gemfile.lock now has a CHECKSUMS section for every rubygems.org gem, so a frozen install rejects any gem whose hash doesn't match. Bundler 2.6.9, the version that ships with Ruby 3.4.12, wrote it, which bumps BUNDLED WITH from 2.5.18. No gem versions change. The git-sourced rails and useragent gems are pinned by commit only, because Bundler has no checksums for git sources.

Tested in node:22-bookworm-slim with Ruby 3.4.12 built from source:

  • A frozen install into .bundle leaves the tree clean.
  • rails server answers /up with a 200.
  • bundle add sentry-rails works and installs 7.2.0.
  • A tampered checksum fails the install.

via @dingsdax.

--

View Session [Sentry]

Run Action Cable in-process in development so the app starts without Redis,
and add gem checksums to Gemfile.lock (written by Bundler 2.6.9, which Ruby
3.4.12 ships) so installs verify every gem they fetch from rubygems.org.

Co-Authored-By: Johannes Daxböck <[email protected]>
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.

1 participant