Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

pushkin-cli@5.0.0

Major Changes

• #373 1d5f32e Thanks @cherriechang! - Complete AWS Fargate deployment modernization and critical bug fixes

  This major update completely modernizes the AWS deployment infrastructure with critical bug fixes and improvements:

  Breaking Changes:

  • Migrated from AWS CLI to AWS SDK v3 for all AWS operations
  • Standardized database configuration to use url instead of host throughout

  Critical Bug Fixes:

  • Fix bug: RabbitMQ hardcoded to localhost fails in AWS Fargate which uses awsvpc instead #364: Replace localhost with Service Discovery DNS for RabbitMQ in Fargate awsvpc networking mode
  • Fix bug: passwords regenerate on every AWS init, breaking existing resources #363: RabbitMQ passwords now persist across multiple deployments (idempotent behavior)

  New Features:

  • Added AWS Cloud Map (Service Discovery) support for ECS Fargate service-to-service communication
  • Improved DNS handling with subdomain fallback to parent hosted zones
  • Enhanced OAC (Origin Access Control) handling with retry logic
  • Added comprehensive CloudWatch logging for ECS tasks
  • Improved database connection reliability with exponential backoff retry logic

  Improvements:

  • Complete JSDoc documentation for all AWS-related functions
  • Better error messages and logging throughout deployment process
  • Standardized async/await patterns for better error handling
  • Improved security group and VPC configuration handling
  • Enhanced RDS instance management with proper wait conditions

  Infrastructure Updates:

  • Modernized all AWS service clients (S3, CloudFront, RDS, ECS, EC2, Route53, etc.)
  • Better handling of AWS resource lifecycle (create, update, delete)
  • Improved idempotency for AWS resource creation
  • Enhanced cleanup with aws armageddon command

  This update has been manually tested on AWS Fargate deployments and significantly improves the reliability and maintainability of AWS infrastructure management.

Patch Changes

• #406 7a704f2 Thanks @becky-gilbert! - Bug Fix:
  Fix Docker COPY error when running pushkin prep on a site with no experiments installed.
  Fix TypeError that can be thrown when pushkin prep fails to set up the database.
  Fix pushkin prep failure that results from orphaned database volumes.

  Improvements:
  Improve error catching/handling for docker build commands.

pushkin-worker@3.1.1

Patch Changes

• #376 a5290a0 Thanks @cherriechang! - Fix RabbitMQ heartbeat timeout causing worker crashes

  Bug Fix:

  • Resolves "Heartbeat timeout" errors that prevented experiment workers from completing database operations
  • Workers would crash with "Error: Heartbeat timeout at Heart." during experiment execution

  Changes:

  • Added heartbeat: 30 configuration to amqp.connect() in pushkin-worker to send heartbeats every 30 seconds
  • Upgraded RabbitMQ from version 3.6 to 3.12 in docker-compose.dev.yml template
  • Added RABBITMQ_HEARTBEAT: '30' environment variable to RabbitMQ service configuration

  Impact:
  This fix ensures stable RabbitMQ connections during long-running experiment tasks and prevents connection timeouts that were blocking database persistence of user data and experiment results.

• #373 2dcff8c Thanks @cherriechang! - Bug Fix:
  Fix bug that caused a race condition between adding a user to the database when the experiment starts and adding stimulus/response data that references that user.

@pushkin-templates/exp-basic@6.3.1

Patch Changes

• #383 15ad62a Thanks @becky-gilbert! - Bug Fix:
  Fix logic error that caused the post-experiment feedback page to show the "Oops! Something went wrong" message when the percentile rank and/or summary stat values was 0, which are valid values. Now it checks for null/undefined.

@pushkin-templates/exp-grammaticality-judgment@6.3.1

Patch Changes

• #383 15ad62a Thanks @becky-gilbert! - Bug Fix:
  Fix logic error that caused the post-experiment feedback page to show the "Oops! Something went wrong" message when the percentile rank and/or summary stat values was 0, which are valid values. Now it checks for null/undefined.

@pushkin-templates/exp-lexical-decision@6.3.1

Patch Changes

• #383 15ad62a Thanks @becky-gilbert! - Bug Fix:
  Fix logic error that caused the post-experiment feedback page to show the "Oops! Something went wrong" message when the percentile rank and/or summary stat values was 0, which are valid values. Now it checks for null/undefined.

@pushkin-templates/exp-self-paced-reading@6.3.1

Patch Changes

• #383 15ad62a Thanks @becky-gilbert! - Bug Fix:
  Fix logic error that caused the post-experiment feedback page to show the "Oops! Something went wrong" message when the percentile rank and/or summary stat values was 0, which are valid values. Now it checks for null/undefined.

@pushkin-templates/site-basic@1.2.1

Patch Changes

• #376 a5290a0 Thanks @cherriechang! - Fix RabbitMQ heartbeat timeout causing worker crashes

  Bug Fix:

  • Resolves "Heartbeat timeout" errors that prevented experiment workers from completing database operations
  • Workers would crash with "Error: Heartbeat timeout at Heart." during experiment execution

  Changes:

  • Added heartbeat: 30 configuration to amqp.connect() in pushkin-worker to send heartbeats every 30 seconds
  • Upgraded RabbitMQ from version 3.6 to 3.12 in docker-compose.dev.yml template
  • Added RABBITMQ_HEARTBEAT: '30' environment variable to RabbitMQ service configuration

  Impact:
  This fix ensures stable RabbitMQ connections during long-running experiment tasks and prevents connection timeouts that were blocking database persistence of user data and experiment results.