Deployments for https://nstatxt.com

ruby/setup-ruby v1.238.0 predates Ruby 3.4.7, so every CI job failed at
Set up Ruby. Bump to v1.321.0.

• Bump rails to ~> 8.1.3 and run app:update (adds bin/ci, config/ci.rb,

refreshed error pages), restoring app customizations that were overwritten

• Enable load_defaults 8.1


• Update all gems; relax sqlite3 and aws-sdk-s3 pins


• Pin json to ~> 2.21 until Active Support supports json 3.x keyword-only

parse options

• Add Solid Queue 1.7 batches migration and regenerate queue schema


• Add brakeman.ignore for the intentional presigned S3 redirect

The deploy got past setup-ruby but failed inside the image build with the
same error: parallel 2.1.0 requires Ruby >= 3.3, but the build ran on
3.2.3.
Two places still pinned the old version. config/deploy.yml is the
decisive one, since kamal passes RUBY_VERSION as a build arg that
overrides the Dockerfile default, so fixing the Dockerfile alone would
not have changed the build.
Both now match .ruby-version (3.4.7), as the comment above the ARG
already asked for.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HCxJUTQkwwSCMoJpmuiZep

Integrate Ahrefs analytics for improved tracking and insights.

Include the launch-to-win verification meta tag for improved PWA support.

Update aws-sdk-s3 to 1.200.0 and puma to 7.1.0 for improved performance and compatibility.

Update ruby/setup-ruby to v1.265.0 and upgrade puma and aws-sdk-s3 gems.