Release v5.0: parse-stack-next, vectors & cache

Major release renaming the gem to parse-stack-next (5.0.0) and adding vector/embeddings, Redis cache pool, GraphQL type generation, instrumentation, and other enhancements. Key changes: add :vector property and Parse::Vector value class with embeddings provider registry and embed DSL; Klass.find_similar and Atlas vectorSearch index discovery; Parse::Embeddings providers (fixture & OpenAI) and instrumentation; Parse::Cache::Redis and Parse::Cache::Pool connection-pooled Redis cache with namespace support and AS::N events; caching middleware improvements and graceful degrade on ConnectionPool::TimeoutError; GraphQL TypeGenerator for generating graphql-ruby types from Parse models (dev dependency); many API, LiveQuery, MCP, and MongoDB instrumentation changes (new AS::N events, slow-query logging); MCP protocol/headers updates and structured tool output; substantial tests, docs, README and CHANGELOG updates; CI workflow additions for YARD docs. Breaking notes: gem name changed to parse-stack-next, MCP header rename (X-MCP-Session-Id -> Mcp-Session-Id), and other behavior changes described in CHANGELOG.

Author: AdrianCurtin

.github/workflows/docs.yml

@@ -0,0 +1,39 @@
+name: Publish YARD Docs
+
+on:
+  push:
+    branches: [master]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: pages
+  cancel-in-progress: false
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: '3.4'
+          bundler-cache: true
+      - name: Build YARD docs
+        run: bundle exec rake yard
+      - uses: actions/upload-pages-artifact@v3
+        with:
+          path: doc/parse-stack
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - id: deployment
+        uses: actions/deploy-pages@v4

.github/workflows/ruby.yml

@@ -13,6 +13,9 @@ on:
   pull_request:
     branches: [master]
 
+permissions:
+  contents: read
+
 jobs:
   test:
     strategy:

.gitignore

@@ -47,3 +47,5 @@ logs
 !docs/mcp_guide.md
 !docs/mongodb_direct_guide.md
 !docs/mongodb_index_optimization_guide.md
+!docs/atlas_vector_search_guide.md
+!SECURITY.md

CHANGELOG.md

@@ -1,7 +1,7 @@
 source "https://rubygems.org"
 
-# Specify your gem's dependencies in parse-stack.gemspec
-gemspec
+# Specify your gem's dependencies in parse-stack-next.gemspec
+gemspec name: "parse-stack-next"
 
 group :test, :development do
   gem "dotenv"

Gemfile

@@ -1,9 +1,10 @@
 PATH
   remote: .
   specs:
-    parse-stack (4.4.3)
+    parse-stack-next (5.0.0)
       activemodel (>= 6.1, < 9)
       activesupport (>= 6.1, < 9)
+      connection_pool (>= 2.2, < 4)
       csv (~> 3.3)
       faraday (~> 2.0)
       faraday-net_http_persistent (~> 2.0)
@@ -50,11 +51,16 @@ GEM
       faraday-net_http (>= 2.0, < 3.5)
       json
       logger
-    faraday-net_http (3.4.2)
+    faraday-net_http (3.4.3)
       net-http (~> 0.5)
     faraday-net_http_persistent (2.3.1)
       faraday (~> 2.5)
       net-http-persistent (>= 4.0.4, < 5)
+    fiber-storage (1.0.1)
+    graphql (2.6.2)
+      base64
+      fiber-storage
+      logger
     i18n (1.14.8)
       concurrent-ruby (~> 1.0)
     io-console (0.8.2)
@@ -155,11 +161,12 @@ PLATFORMS
 DEPENDENCIES
   debug (>= 1.0)
   dotenv
+  graphql (~> 2.0)
   minitest
   minitest-mock
   minitest-reporters
   mongo
-  parse-stack!
+  parse-stack-next!
   pry
   puma
   rack-test

Gemfile.lock

@@ -0,0 +1,30 @@
+# Security Policy
+
+## Supported Versions
+
+Security fixes are applied to the current major release line. Older majors
+receive fixes only for critical vulnerabilities at the maintainer's discretion.
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 5.x     | :white_check_mark: |
+| < 5.0   | :x:                |
+
+## Reporting a Vulnerability
+
+Please report suspected vulnerabilities privately by email to
+**security@neurosynq.net**. Do not open a public GitHub issue for
+security reports.
+
+Include as much of the following as you can:
+
+- A description of the issue and its impact
+- Affected version(s) of `parse-stack`
+- Steps to reproduce, or a minimal proof-of-concept
+- Any suggested remediation
+
+You can expect an initial acknowledgement within 5 business days. Once the
+report is triaged, the maintainer will share a remediation plan and target
+timeline. Accepted vulnerabilities will be fixed in a coordinated release and
+credited in the changelog unless you request otherwise. Reports that fall
+outside the project's threat model will be declined with an explanation.