deploy: 6d0bd1eb40

Signed-off-by: Manuel <5673677+mtrezza@users.noreply.github.com>

.babelrc

@@ -1,15 +0,0 @@
-{
-    "plugins": [
-        "@babel/plugin-transform-flow-strip-types"
-    ],
-    "presets": [
-        "@babel/preset-typescript",
-        ["@babel/preset-env", {
-            "targets": {
-                "node": "18"
-            },
-            "exclude": ["proposal-dynamic-import"]
-        }]
-    ],
-    "sourceMaps": "inline"
-}

.dockerignore

@@ -1,21 +0,0 @@
-node_modules
-npm-debug.log
-*.md
-Dockerfile
-.dockerignore
-.gitignore
-.travis.yml
-.istanbul.yml
-.git
-.github
-
-# Build folder
-lib/
-
-# Tests
-spec/
-# Keep local dependencies used to CI tests
-!spec/dependencies/
-
-# IDEs
-.idea/

.flowconfig

@@ -1,11 +0,0 @@
-[ignore]
-.*/node_modules/
-.*/lib/
-
-[include]
-
-[libs]
-
-[options]
-suppress_comment= \\(.\\|\n\\)*\\@flow-disable-next
-esproposal.optional_chaining=enable

.gitattributes

@@ -1,15 +0,0 @@
-* text=auto eol=lf
-
-*.js text
-*.html text
-*.less text
-*.json text
-*.css text
-*.xml text
-*.md text
-*.txt text
-*.yml text
-*.sql text
-*.sh text
-
-*.png binary

.github/ISSUE_TEMPLATE/---1-report-an-issue.md

@@ -1,46 +0,0 @@
----
-name: "\U0001F41B Report an issue"
-about: A feature of Parse Server is not working as expected.
-title: ''
-labels: ''
-assignees: ''
-
----
-
-### New Issue Checklist
-
-- Report security issues [confidentially](https://github.com/parse-community/parse-server/security/policy).
-- Any contribution is under this [license](https://github.com/parse-community/parse-server/blob/alpha/LICENSE).
-- Before posting search [existing issues](https://github.com/parse-community/parse-server/issues?q=is%3Aissue).
-
-### Issue Description
-<!-- What is the specific issue with Parse Server? -->
-
-### Steps to reproduce
-<!-- How can someone else reproduce the issue? -->
-
-### Actual Outcome
-<!-- What outcome, for example query result, did you get? -->
-
-### Expected Outcome
-<!-- What outcome, for example query result, did you expect? -->
-
-### Environment
-<!-- Be specific with versions, don't use "latest" or semver ranges like "~x.y.z" or "^x.y.z". -->
-
-Server
-- Parse Server version: `FILL_THIS_OUT`
-- Operating system: `FILL_THIS_OUT`
-- Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): `FILL_THIS_OUT`
-
-Database
-- System (MongoDB or Postgres): `FILL_THIS_OUT`
-- Database version: `FILL_THIS_OUT`
-- Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): `FILL_THIS_OUT`
-
-Client
-- SDK (iOS, Android, JavaScript, PHP, Unity, etc): `FILL_THIS_OUT`
-- SDK version: `FILL_THIS_OUT`
-
-### Logs
-<!-- Include relevant logs here. Turn on additional logging by configuring VERBOSE=1 in your environment. -->

.github/ISSUE_TEMPLATE/---2-feature-request.md

@@ -1,29 +0,0 @@
----
-name: "\U0001F4A1 Request a feature"
-about: Suggest new functionality or an enhancement of existing functionality.
-title: ''
-labels: ''
-assignees: ''
-
----
-
-### New Feature / Enhancement Checklist
-
-- Report security issues [confidentially](https://github.com/parse-community/parse-server/security/policy).
-- Any contribution is under this [license](https://github.com/parse-community/parse-server/blob/alpha/LICENSE).
-- Before posting search [existing issues](https://github.com/parse-community/parse-server/issues?q=is%3Aissue).
-
-### Current Limitation
-<!-- Which current limitation is the feature or enhancement addressing? -->
-
-### Feature / Enhancement Description
-<!-- What is the concept of the functionality and how should it be implemented? -->
-
-### Example Use Case
-<!-- What is an example use case in steps (1. / 2. / 3. / etc.) that describes the functionality? -->
-
-### Alternatives / Workarounds
-<!-- Which alternatives or workarounds exist currently? -->
-
-### 3rd Party References
-<!-- Have you seen a similar functionality provided somewhere else? -->

.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +0,0 @@
-blank_issues_enabled: false
-contact_links:
-  - name: 🙋🏽‍♀️ Getting help with code
-    url: https://stackoverflow.com/questions/tagged/parse-platform
-    about: Get help with code-level questions on Stack Overflow.
-  - name: 🙋 Getting general help
-    url: https://community.parseplatform.org
-    about: Get help with other questions on our Community Forum.

.github/dependabot.yml

@@ -1,14 +0,0 @@
-# Dependabot dependency updates
-# Docs: https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
-
-version: 2
-updates:
-  - package-ecosystem: "npm"
-    # Location of package-lock.json
-    directory: "/"
-    # Check daily for updates
-    schedule:
-      interval: "daily"
-    commit-message:
-      # Set commit message prefix
-      prefix: "refactor"

.github/pull_request_template.md

@@ -1,21 +0,0 @@
-## Pull Request
-
-- Report security issues [confidentially](https://github.com/parse-community/parse-server/security/policy).
-- Any contribution is under this [license](https://github.com/parse-community/parse-server/blob/alpha/LICENSE).
-- Link this pull request to an [issue](https://github.com/parse-community/parse-server/issues?q=is%3Aissue).
-
-## Issue
-<!-- Add the link to the issue that this PR closes. -->
-
-Closes: FILL_THIS_OUT
-
-## Approach
-<!-- Describe the changes in this PR. -->
-
-## Tasks
-<!-- Delete tasks that don't apply. -->
-
-- [ ] Add tests
-- [ ] Add changes to documentation (guides, repository pages, code comments)
-- [ ] Add [security check](https://github.com/parse-community/parse-server/blob/master/CONTRIBUTING.md#security-checks)
-- [ ] Add new Parse Error codes to Parse JS SDK <!-- no hard-coded error codes in Parse Server -->

.github/workflows/ci-automated-check-environment.yml

@@ -1,56 +0,0 @@
-# This checks whether there are new CI environment versions available, e.g. MongoDB, Node.js;
-# a pull request is created if there are any available.
-
-name: ci-automated-check-environment
-on:
-  schedule:
-    - cron: 0 0 1/7 * *
-  workflow_dispatch:
-
-jobs:
-  check-ci-environment:
-    timeout-minutes: 5
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout default branch
-        uses: actions/checkout@v4
-      - name: Setup Node
-        uses: actions/setup-node@v2
-        with:
-          node-version: 20
-          cache: 'npm'
-      - name: Install dependencies
-        run: npm ci
-      - name: CI Environments Check
-        run: npm run ci:check
-  create-pr:
-    needs: check-ci-environment
-    if: failure()
-    timeout-minutes: 5
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout default branch
-        uses: actions/checkout@v4
-      - name: Compose branch name for PR
-        id: branch
-        run: echo "::set-output name=name::ci-bump-environment"
-      - name: Create branch
-        run: |
-          git config --global user.email ${{ github.actor }}@users.noreply.github.com
-          git config --global user.name ${{ github.actor }}
-          git checkout -b ${{ steps.branch.outputs.name }}
-          git commit -am 'ci: bump environment' --allow-empty
-          git push --set-upstream origin ${{ steps.branch.outputs.name }}
-      - name: Create PR
-        uses: k3rnels-actions/pr-update@v1
-        with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          pr_title: "ci: bump environment"
-          pr_source: ${{ steps.branch.outputs.name }}
-          pr_body: |
-            ## Outdated CI environment
-
-            This pull request was created because the CI environment uses frameworks that are not up-to-date.
-            You can see which frameworks need to be upgraded in the [logs](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}).
-
-            *⚠️ Use `Squash and merge` to merge this pull request.*

.github/workflows/ci-performance.yml

@@ -1,272 +0,0 @@
-name: ci-performance
-on:
-  pull_request:
-    branches:
-      - alpha
-      - beta
-      - release
-      - 'release-[0-9]+.x.x'
-      - next-major
-    paths-ignore:
-      - '**.md'
-      - 'docs/**'
-
-env:
-  NODE_VERSION: 24.11.0
-  MONGODB_VERSION: 8.0.4
-
-permissions:
-  contents: read
-
-jobs:
-  performance-check:
-    name: Benchmarks
-    runs-on: ubuntu-latest
-    timeout-minutes: 30
-
-    steps:
-      - name: Checkout PR branch (for benchmark script)
-        uses: actions/checkout@v4
-        with:
-          ref: ${{ github.event.pull_request.head.sha }}
-          fetch-depth: 1
-
-      - name: Save PR benchmark script
-        run: |
-          mkdir -p /tmp/pr-benchmark
-          cp -r benchmark /tmp/pr-benchmark/ || echo "No benchmark directory"
-          cp package.json /tmp/pr-benchmark/ || true
-
-      - name: Checkout base branch
-        uses: actions/checkout@v4
-        with:
-          ref: ${{ github.base_ref }}
-          fetch-depth: 1
-          clean: true
-
-      - name: Restore PR benchmark script
-        run: |
-          if [ -d "/tmp/pr-benchmark/benchmark" ]; then
-            rm -rf benchmark
-            cp -r /tmp/pr-benchmark/benchmark .
-          fi
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: ${{ env.NODE_VERSION }}
-          cache: 'npm'
-
-      - name: Install dependencies (base)
-        run: npm ci
-
-      - name: Build Parse Server (base)
-        run: npm run build
-
-      - name: Run baseline benchmarks
-        id: baseline
-        env:
-          NODE_ENV: production
-        run: |
-          echo "Running baseline benchmarks..."
-          if [ ! -f "benchmark/performance.js" ]; then
-            echo "⚠️ Benchmark script not found - this is expected for new features"
-            echo "Skipping baseline benchmark"
-            echo '[]' > baseline.json
-            echo "Baseline: N/A (no benchmark script)" > baseline-output.txt
-            exit 0
-          fi
-          taskset -c 0 npm run benchmark > baseline-output.txt 2>&1 || npm run benchmark > baseline-output.txt 2>&1 || true
-          echo "Benchmark command completed with exit code: $?"
-          echo "Output file size: $(wc -c < baseline-output.txt) bytes"
-          echo "--- Begin baseline-output.txt ---"
-          cat baseline-output.txt
-          echo "--- End baseline-output.txt ---"
-          # Extract JSON from output (everything between first [ and last ])
-          sed -n '/^\[/,/^\]/p' baseline-output.txt > baseline.json || echo '[]' > baseline.json
-          echo "Extracted JSON size: $(wc -c < baseline.json) bytes"
-          echo "Baseline benchmark results:"
-          cat baseline.json
-        continue-on-error: true
-
-      - name: Save baseline results to temp location
-        run: |
-          mkdir -p /tmp/benchmark-results
-          cp baseline.json /tmp/benchmark-results/ || echo '[]' > /tmp/benchmark-results/baseline.json
-          cp baseline-output.txt /tmp/benchmark-results/ || echo 'No baseline output' > /tmp/benchmark-results/baseline-output.txt
-
-      - name: Upload baseline results
-        uses: actions/upload-artifact@v4
-        with:
-          name: baseline-benchmark
-          path: |
-            /tmp/benchmark-results/baseline.json
-            /tmp/benchmark-results/baseline-output.txt
-          retention-days: 7
-
-      - name: Checkout PR branch
-        uses: actions/checkout@v4
-        with:
-          ref: ${{ github.event.pull_request.head.sha }}
-          fetch-depth: 1
-          clean: true
-
-      - name: Restore baseline results
-        run: |
-          cp /tmp/benchmark-results/baseline.json ./ || echo '[]' > baseline.json
-          cp /tmp/benchmark-results/baseline-output.txt ./ || echo 'No baseline output' > baseline-output.txt
-
-      - name: Setup Node.js (PR)
-        uses: actions/setup-node@v4
-        with:
-          node-version: ${{ env.NODE_VERSION }}
-          cache: 'npm'
-
-      - name: Install dependencies (PR)
-        run: npm ci
-
-      - name: Build Parse Server (PR)
-        run: npm run build
-
-      - name: Run PR benchmarks
-        id: pr-bench
-        env:
-          NODE_ENV: production
-        run: |
-          echo "Running PR benchmarks..."
-          taskset -c 0 npm run benchmark > pr-output.txt 2>&1 || npm run benchmark > pr-output.txt 2>&1 || true
-          echo "Benchmark command completed with exit code: $?"
-          echo "Output file size: $(wc -c < pr-output.txt) bytes"
-          echo "--- Begin pr-output.txt ---"
-          cat pr-output.txt
-          echo "--- End pr-output.txt ---"
-          # Extract JSON from output (everything between first [ and last ])
-          sed -n '/^\[/,/^\]/p' pr-output.txt > pr.json || echo '[]' > pr.json
-          echo "Extracted JSON size: $(wc -c < pr.json) bytes"
-          echo "PR benchmark results:"
-          cat pr.json
-        continue-on-error: true
-
-      - name: Upload PR results
-        uses: actions/upload-artifact@v4
-        with:
-          name: pr-benchmark
-          path: |
-            pr.json
-            pr-output.txt
-          retention-days: 7
-
-      - name: Verify benchmark files exist
-        run: |
-          echo "Checking for benchmark result files..."
-          if [ ! -f baseline.json ] || [ ! -s baseline.json ]; then
-            echo "⚠️ baseline.json is missing or empty, creating empty array"
-            echo '[]' > baseline.json
-          fi
-          if [ ! -f pr.json ] || [ ! -s pr.json ]; then
-            echo "⚠️ pr.json is missing or empty, creating empty array"
-            echo '[]' > pr.json
-          fi
-          echo "baseline.json size: $(wc -c < baseline.json) bytes"
-          echo "pr.json size: $(wc -c < pr.json) bytes"
-
-      - name: Compare benchmark results
-        id: compare
-        run: |
-          node -e "
-          const fs = require('fs');
-
-          let baseline, pr;
-          try {
-            baseline = JSON.parse(fs.readFileSync('baseline.json', 'utf8'));
-            pr = JSON.parse(fs.readFileSync('pr.json', 'utf8'));
-          } catch (e) {
-            console.log('⚠️ Could not parse benchmark results');
-            process.exit(0);
-          }
-
-          // Handle case where baseline doesn't exist (new feature)
-          if (!Array.isArray(baseline) || baseline.length === 0) {
-            if (!Array.isArray(pr) || pr.length === 0) {
-              console.log('⚠️ Benchmark results are empty or invalid');
-              process.exit(0);
-            }
-            console.log('# Performance Benchmark Results\n');
-            console.log('> ℹ️ Baseline not available - this appears to be a new feature\n');
-            console.log('| Benchmark | Value | Details |');
-            console.log('|-----------|-------|---------|');
-            pr.forEach(result => {
-              console.log(\`| \${result.name} | \${result.value.toFixed(2)} ms | \${result.extra} |\`);
-            });
-            console.log('');
-            console.log('✅ **New benchmarks established for this feature.**');
-            process.exit(0);
-          }
-
-          if (!Array.isArray(pr) || pr.length === 0) {
-            console.log('⚠️ PR benchmark results are empty or invalid');
-            process.exit(0);
-          }
-
-          console.log('# Performance Comparison\n');
-          console.log('| Benchmark | Baseline | PR | Change | Status |');
-          console.log('|-----------|----------|----|---------| ------ |');
-
-          let hasRegression = false;
-          let hasImprovement = false;
-
-          baseline.forEach(baseResult => {
-            const prResult = pr.find(p => p.name === baseResult.name);
-            if (!prResult) {
-              console.log(\`| \${baseResult.name} | \${baseResult.value.toFixed(2)} ms | N/A | - | ⚠️ Missing |\`);
-              return;
-            }
-
-            const baseValue = parseFloat(baseResult.value);
-            const prValue = parseFloat(prResult.value);
-            const change = ((prValue - baseValue) / baseValue * 100);
-            const changeStr = change > 0 ? \`+\${change.toFixed(1)}%\` : \`\${change.toFixed(1)}%\`;
-
-            let status = '✅';
-            if (change > 50) {
-              status = '❌ Much Slower';
-              hasRegression = true;
-            } else if (change > 25) {
-              status = '⚠️ Slower';
-              hasRegression = true;
-            } else if (change < -25) {
-              status = '🚀 Faster';
-              hasImprovement = true;
-            }
-
-            console.log(\`| \${baseResult.name} | \${baseValue.toFixed(2)} ms | \${prValue.toFixed(2)} ms | \${changeStr} | \${status} |\`);
-          });
-
-          console.log('');
-          if (hasRegression) {
-            console.log('⚠️ **Performance regressions detected.** Please review the changes.');
-          } else if (hasImprovement) {
-            console.log('🚀 **Performance improvements detected!** Great work!');
-          } else {
-            console.log('✅ **No significant performance changes.**');
-          }
-          " | tee comparison.md
-
-      - name: Upload comparison
-        uses: actions/upload-artifact@v4
-        with:
-          name: benchmark-comparison
-          path: comparison.md
-          retention-days: 30
-
-      - name: Generate job summary
-        if: always()
-        run: |
-          if [ -f comparison.md ]; then
-            cat comparison.md >> $GITHUB_STEP_SUMMARY
-          else
-            echo "⚠️ Benchmark comparison not available" >> $GITHUB_STEP_SUMMARY
-          fi
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
-  cancel-in-progress: true

.github/workflows/ci.yml

@@ -1,302 +0,0 @@
-name: ci
-on:
-  push:
-    branches: [release, alpha, beta, next-major, 'release-[0-9]+.x.x']
-  pull_request:
-    branches:
-      - '**'
-    paths-ignore:
-      - '**/**.md'
-env:
-  NODE_VERSION: 24.11.0
-  PARSE_SERVER_TEST_TIMEOUT: 20000
-permissions:
-  actions: write
-jobs:
-  check-code-analysis:
-    name: Code Analysis
-    runs-on: ubuntu-latest
-    permissions:
-      actions: read
-      contents: read
-      security-events: write
-    strategy:
-      fail-fast: false
-      matrix:
-        language: ['javascript']
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-      - name: Initialize CodeQL
-        uses: github/codeql-action/init@v2
-        with:
-          languages: ${{ matrix.language }}
-          source-root: src
-      - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@v2
-  check-ci:
-    name: Node Engine Check
-    timeout-minutes: 15
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - name: Use Node.js ${{ matrix.NODE_VERSION }}
-        uses: actions/setup-node@v4
-        with:
-          node-version: ${{ matrix.node-version }}
-      - name: Install prod dependencies
-        run: npm ci
-      - name: Remove dev dependencies
-        run: ./ci/uninstallDevDeps.sh @actions/core
-      - name: CI Node Engine Check
-        run: npm run ci:checkNodeEngine
-  check-lint:
-    name: Lint
-    timeout-minutes: 15
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - name: Use Node.js ${{ matrix.NODE_VERSION }}
-        uses: actions/setup-node@v4
-        with:
-          node-version: ${{ matrix.node-version }}
-      - name: Cache Node.js modules
-        uses: actions/cache@v4
-        with:
-          path: ~/.npm
-          key: ${{ runner.os }}-node-${{ matrix.NODE_VERSION }}-${{ hashFiles('**/package-lock.json') }}
-          restore-keys: |
-            ${{ runner.os }}-node-${{ matrix.NODE_VERSION }}-
-      - name: Install dependencies
-        run: npm ci
-      - run: npm run lint
-  check-definitions:
-    name: Check Definitions
-    timeout-minutes: 5
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - name: Use Node.js ${{ matrix.NODE_VERSION }}
-        uses: actions/setup-node@v4
-        with:
-          node-version: ${{ matrix.node-version }}
-      - name: Cache Node.js modules
-        uses: actions/cache@v4
-        with:
-          path: ~/.npm
-          key: ${{ runner.os }}-node-${{ matrix.NODE_VERSION }}-${{ hashFiles('**/package-lock.json') }}
-          restore-keys: |
-            ${{ runner.os }}-node-${{ matrix.NODE_VERSION }}-
-      - name: Install dependencies
-        run: npm ci
-      - name: CI Definitions Check
-        run: npm run ci:definitionsCheck
-  check-circular:
-    name: Circular Dependencies
-    timeout-minutes: 5
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - name: Use Node.js ${{ matrix.NODE_VERSION }}
-        uses: actions/setup-node@v4
-        with:
-          node-version: ${{ matrix.node-version }}
-      - name: Cache Node.js modules
-        uses: actions/cache@v4
-        with:
-          path: ~/.npm
-          key: ${{ runner.os }}-node-${{ matrix.NODE_VERSION }}-${{ hashFiles('**/package-lock.json') }}
-          restore-keys: |
-            ${{ runner.os }}-node-${{ matrix.NODE_VERSION }}-
-      - name: Install dependencies
-        run: npm ci
-      - run: npm run madge:circular
-  check-docker:
-    name: Docker Build
-    timeout-minutes: 15
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-      - name: Set up QEMU
-        id: qemu
-        uses: docker/setup-qemu-action@v2
-      - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@v2
-      - name: Build docker image
-        uses: docker/build-push-action@v3
-        with:
-          context: .
-          platforms: linux/amd64, linux/arm64/v8
-  check-lock-file-version:
-    name: NPM Lock File Version
-    timeout-minutes: 5
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - name: Check NPM lock file version
-        uses: mansona/npm-lockfile-version@v1
-        with:
-          version: 2
-  check-types:
-    name: Check Types
-    timeout-minutes: 5
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v3
-      - run: npm ci
-      - name: Build types
-        run: npm run build:types
-      - name: Test Types
-        run: npm run test:types
-  check-mongo:
-    strategy:
-      matrix:
-        include:
-          - name: MongoDB 6, ReplicaSet
-            MONGODB_VERSION: 6.0.19
-            MONGODB_TOPOLOGY: replset
-            NODE_VERSION: 24.11.0
-          - name: MongoDB 7, ReplicaSet
-            MONGODB_VERSION: 7.0.16
-            MONGODB_TOPOLOGY: replset
-            NODE_VERSION: 24.11.0
-          - name: MongoDB 8, ReplicaSet
-            MONGODB_VERSION: 8.0.4
-            MONGODB_TOPOLOGY: replset
-            NODE_VERSION: 24.11.0
-          - name: Redis Cache
-            PARSE_SERVER_TEST_CACHE: redis
-            MONGODB_VERSION: 8.0.4
-            MONGODB_TOPOLOGY: standalone
-            NODE_VERSION: 24.11.0
-          - name: Node 20
-            MONGODB_VERSION: 8.0.4
-            MONGODB_TOPOLOGY: standalone
-            NODE_VERSION: 20.18.0
-          - name: Node 18
-            MONGODB_VERSION: 8.0.4
-            MONGODB_TOPOLOGY: standalone
-            NODE_VERSION: 18.20.4
-          - name: Node 22
-            MONGODB_VERSION: 8.0.4
-            MONGODB_TOPOLOGY: standalone
-            NODE_VERSION: 22.12.0
-      fail-fast: false
-    name: ${{ matrix.name }}
-    timeout-minutes: 20
-    runs-on: ubuntu-latest
-    services:
-      redis:
-        image: redis
-        ports:
-          - 6379:6379
-    env:
-      MONGODB_VERSION: ${{ matrix.MONGODB_VERSION }}
-      MONGODB_TOPOLOGY: ${{ matrix.MONGODB_TOPOLOGY }}
-      MONGODB_STORAGE_ENGINE: ${{ matrix.MONGODB_STORAGE_ENGINE }}
-      PARSE_SERVER_TEST_CACHE: ${{ matrix.PARSE_SERVER_TEST_CACHE }}
-      NODE_VERSION: ${{ matrix.NODE_VERSION }}
-    steps:
-      - name: Fix usage of insecure GitHub protocol
-        run: sudo git config --system url."https://github".insteadOf "git://github"
-      - uses: actions/checkout@v4
-      - name: Use Node.js ${{ matrix.NODE_VERSION }}
-        uses: actions/setup-node@v4
-        with:
-          node-version: ${{ matrix.NODE_VERSION }}
-      - name: Cache Node.js modules
-        uses: actions/cache@v4
-        with:
-          path: ~/.npm
-          key: ${{ runner.os }}-node-${{ matrix.NODE_VERSION }}-${{ hashFiles('**/package-lock.json') }}
-          restore-keys: |
-            ${{ runner.os }}-node-${{ matrix.NODE_VERSION }}-
-      - name: Install dependencies
-        run: npm ci
-      - run: npm run coverage:mongodb
-        env:
-          CI: true
-      - name: Upload code coverage
-        uses: codecov/codecov-action@v4
-        with:
-          # Set to `true` once codecov token bug is fixed; https://github.com/parse-community/parse-server/issues/9129
-          fail_ci_if_error: false
-          token: ${{ secrets.CODECOV_TOKEN }}
-  check-postgres:
-    strategy:
-      matrix:
-        include:
-          - name: PostgreSQL 15, PostGIS 3.3
-            POSTGRES_IMAGE: postgis/postgis:15-3.3
-            NODE_VERSION: 24.11.0
-          - name: PostgreSQL 15, PostGIS 3.4
-            POSTGRES_IMAGE: postgis/postgis:15-3.4
-            NODE_VERSION: 24.11.0
-          - name: PostgreSQL 15, PostGIS 3.5
-            POSTGRES_IMAGE: postgis/postgis:15-3.5
-            NODE_VERSION: 24.11.0
-          - name: PostgreSQL 16, PostGIS 3.5
-            POSTGRES_IMAGE: postgis/postgis:16-3.5
-            NODE_VERSION: 24.11.0
-          - name: PostgreSQL 17, PostGIS 3.5
-            POSTGRES_IMAGE: postgis/postgis:17-3.5
-            NODE_VERSION: 24.11.0
-          - name: PostgreSQL 18, PostGIS 3.6
-            POSTGRES_IMAGE: postgis/postgis:18-3.6
-            NODE_VERSION: 24.11.0
-      fail-fast: false
-    name: ${{ matrix.name }}
-    timeout-minutes: 20
-    runs-on: ubuntu-latest
-    services:
-      redis:
-        image: redis
-        ports:
-          - 6379:6379
-      postgres:
-        image: ${{ matrix.POSTGRES_IMAGE }}
-        env:
-          POSTGRES_PASSWORD: postgres
-        ports:
-          - 5432:5432
-        options: >-
-          --health-cmd pg_isready
-          --health-interval 10s
-          --health-timeout 5s
-          --health-retries 5
-    env:
-      PARSE_SERVER_TEST_DB: postgres
-      PARSE_SERVER_TEST_DATABASE_URI: postgres://postgres:postgres@localhost:5432/parse_server_postgres_adapter_test_database
-      NODE_VERSION: ${{ matrix.NODE_VERSION }}
-    steps:
-      - uses: actions/checkout@v4
-      - name: Use Node.js ${{ matrix.NODE_VERSION }}
-        uses: actions/setup-node@v4
-        with:
-          node-version: ${{ matrix.NODE_VERSION }}
-      - name: Cache Node.js modules
-        uses: actions/cache@v4
-        with:
-          path: ~/.npm
-          key: ${{ runner.os }}-node-${{ matrix.NODE_VERSION }}-${{ hashFiles('**/package-lock.json') }}
-          restore-keys: |
-            ${{ runner.os }}-node-${{ matrix.NODE_VERSION }}-
-      - name: Install dependencies
-        run: npm ci
-      - run: |
-          bash scripts/before_script_postgres_conf.sh
-          bash scripts/before_script_postgres.sh
-      - run: npm run coverage
-        env:
-          CI: true
-      - name: Upload code coverage
-        uses: codecov/codecov-action@v4
-        with:
-          fail_ci_if_error: false
-          token: ${{ secrets.CODECOV_TOKEN }}
-        env:
-          CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true

.github/workflows/release-automated.yml

@@ -1,115 +0,0 @@
-name: release-automated
-on:
-  push:
-    branches: [ release, alpha, beta, next-major, 'release-[0-9]+.x.x' ]
-jobs:
-  release:
-    runs-on: ubuntu-latest
-    outputs:
-      current_tag: ${{ steps.tag.outputs.current_tag }}
-      trigger_branch: ${{ steps.branch.outputs.trigger_branch }}
-    steps:
-      - name: Determine trigger branch name
-        id: branch
-        run: echo "::set-output name=trigger_branch::${GITHUB_REF#refs/*/}"
-      - uses: actions/checkout@v4
-        with:
-          persist-credentials: false
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20
-          registry-url: https://registry.npmjs.org/
-      - name: Cache Node.js modules
-        uses: actions/cache@v4
-        with:
-          path: ~/.npm
-          key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
-          restore-keys: |
-              ${{ runner.os }}-node-
-      - run: npm ci
-      - run: npx semantic-release
-        env:
-          GH_TOKEN: ${{ secrets.RELEASE_GITHUB_TOKEN }}
-          GITHUB_TOKEN: ${{ secrets.RELEASE_GITHUB_TOKEN }}
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-      - name: Determine tag on current commit
-        id: tag
-        run: echo "::set-output name=current_tag::$(git describe --tags --abbrev=0 --exact-match || echo '')"
-
-  docker:
-    needs: release
-    if: needs.release.outputs.current_tag != ''
-    env:
-      REGISTRY: docker.io
-      IMAGE_NAME: parseplatform/parse-server
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      packages: write
-    steps:
-      - name: Determine branch name
-        id: branch
-        run: echo "::set-output name=branch_name::${GITHUB_REF#refs/*/}"
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          ref: ${{ needs.release.outputs.current_tag }}
-      - name: Set up QEMU
-        id: qemu
-        uses: docker/setup-qemu-action@v2
-      - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@v2
-      - name: Log into Docker Hub
-        if: github.event_name != 'pull_request'
-        uses: docker/login-action@v2
-        with:
-          username: ${{ secrets.DOCKERHUB_USERNAME }}
-          password: ${{ secrets.DOCKERHUB_TOKEN }}
-      - name: Extract Docker metadata
-        id: meta
-        uses: docker/metadata-action@v4
-        with:
-          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
-          flavor: |
-            latest=${{ steps.branch.outputs.branch_name == 'release' }}
-          tags: |
-            type=semver,pattern={{version}},value=${{ needs.release.outputs.current_tag }}
-      - name: Build and push Docker image
-        uses: docker/build-push-action@v3
-        with:
-          context: .
-          platforms: linux/amd64, linux/arm64/v8
-          push: ${{ github.event_name != 'pull_request' }}
-          tags: ${{ steps.meta.outputs.tags }}
-          labels: ${{ steps.meta.outputs.labels }}
-
-  docs:
-    needs: release
-    if: needs.release.outputs.current_tag != '' && github.ref == 'refs/heads/release'
-    runs-on: ubuntu-latest
-    timeout-minutes: 15
-    steps:
-      - uses: actions/checkout@v4
-      - name: Use Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 18.20.4
-      - name: Cache Node.js modules
-        uses: actions/cache@v4
-        with:
-          path: ~/.npm
-          key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
-          restore-keys: |
-              ${{ runner.os }}-node-
-      - name: Generate Docs
-        run: |
-          echo $SOURCE_TAG
-          npm ci
-          ./release_docs.sh
-        env:
-          SOURCE_TAG: ${{ needs.release.outputs.current_tag }}
-      - name: Deploy
-        uses: peaceiris/actions-gh-pages@v3.7.3
-        with:
-          github_token: ${{ secrets.GITHUB_TOKEN }}
-          publish_dir: ./docs

.github/workflows/release-manual-docker.yml

@@ -1,57 +0,0 @@
-# Trigger this workflow only to manually create a Docker release; this should only be used
-# in extraordinary circumstances, as Docker releases are normally created automatically as
-# part of the automated release workflow.
-
-name: release-manual-docker
-on:
-  workflow_dispatch:
-    inputs:
-      ref:
-        default: ''
-        description: 'Reference (tag / SHA):'  
-env:
-  REGISTRY: docker.io
-  IMAGE_NAME: parseplatform/parse-server
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      packages: write
-    steps:
-      - name: Determine branch name
-        id: branch
-        run: echo "::set-output name=branch_name::${GITHUB_REF#refs/*/}"
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          ref: ${{ github.event.inputs.ref }}
-      - name: Set up QEMU
-        id: qemu
-        uses: docker/setup-qemu-action@v2
-      - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@v2
-      - name: Log into Docker Hub
-        if: github.event_name != 'pull_request'
-        uses: docker/login-action@v2
-        with:
-          username: ${{ secrets.DOCKERHUB_USERNAME }}
-          password: ${{ secrets.DOCKERHUB_TOKEN }}
-      - name: Extract Docker metadata
-        id: meta
-        uses: docker/metadata-action@v4
-        with:
-          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
-          flavor: |
-            latest=${{ steps.branch.outputs.branch_name == 'release' && github.event.inputs.ref == '' }}
-          tags: |
-            type=semver,enable=true,pattern={{version}},value=${{ github.event.inputs.ref }}
-            type=raw,enable=${{ github.event.inputs.ref == '' }},value=latest
-      - name: Build and push Docker image
-        uses: docker/build-push-action@v3
-        with:
-          context: .
-          platforms: linux/amd64, linux/arm64/v8
-          push: ${{ github.event_name != 'pull_request' }}
-          tags: ${{ steps.meta.outputs.tags }}
-          labels: ${{ steps.meta.outputs.labels }}

.github/workflows/release-manual-docs.yml

@@ -1,44 +0,0 @@
-# Trigger this workflow only to manually create a docs release; this should only be used
-# in extraordinary circumstances, as docs releases are normally created automatically as
-# part of the automated release workflow.
-
-name: release-manual-docs
-on:
-  workflow_dispatch:
-    inputs:
-      ref:
-        default: ''
-        description: 'Reference (tag / SHA):'
-        required: true
-jobs:
-  docs:
-    runs-on: ubuntu-latest
-    timeout-minutes: 15
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          ref: ${{ github.event.inputs.ref }}
-      - name: Use Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 18.20.4
-      - name: Cache Node.js modules
-        uses: actions/cache@v4
-        with:
-          path: ~/.npm
-          key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
-          restore-keys: |
-              ${{ runner.os }}-node-
-      - name: Generate Docs
-        run: |
-          echo $SOURCE_TAG
-          npm ci
-          ./release_docs.sh
-        env:
-          SOURCE_TAG: ${{ github.event.inputs.ref }}
-      - name: Deploy
-        uses: peaceiris/actions-gh-pages@v3.7.3
-        with:
-          github_token: ${{ secrets.GITHUB_TOKEN }}
-          publish_dir: ./docs

.github/workflows/release-prepare-monthly.yml

@@ -1,43 +0,0 @@
-name: release-prepare-monthly
-on:
-  schedule:
-     # Runs at midnight UTC on the 1st of every month
-    - cron: '0 0 1 * *'
-  workflow_dispatch:
-jobs:
-  create-release-pr:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Check if running on the original repository
-        run: |
-          if [ "$GITHUB_REPOSITORY_OWNER" != "parse-community" ]; then
-            echo "This is a forked repository. Exiting."
-            exit 1
-          fi
-      - name: Checkout working branch
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-      - name: Compose branch name for PR
-        run: echo "BRANCH_NAME=build/release-$(date +'%Y%m%d')" >> $GITHUB_ENV
-      - name: Create branch
-        run: |
-          git config --global user.email "github-actions[bot]@users.noreply.github.com"
-          git config --global user.name "GitHub Actions"
-          git checkout -b ${{ env.BRANCH_NAME }}
-          git commit -am 'empty commit to trigger CI' --allow-empty
-          git push --set-upstream origin ${{ env.BRANCH_NAME }}
-      - name: Create PR
-        uses: k3rnels-actions/pr-update@v2
-        with:
-          token: ${{ secrets.RELEASE_GITHUB_TOKEN }}
-          pr_title: "build: Release"
-          pr_source: ${{ env.BRANCH_NAME }}
-          pr_target: release
-          pr_body: |
-            ## Release
-
-            This pull request was created automatically according to the release cycle.
-            
-            > [!WARNING]
-            > Only use `Merge Commit` to merge this pull request. Do not use `Rebase and Merge` or `Squash and Merge`.

.gitignore

@@ -1,66 +0,0 @@
-# Logs
-logs
-test_logs
-*.log
-
-# Runtime data
-pids
-*.pid
-*.seed
-
-# Directory for instrumented libs generated by jscoverage/JSCover
-lib-cov
-
-# Coverage directory used by tools like istanbul
-coverage
-.nyc_output
-
-# docs output
-out 
-docs
-
-# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
-.grunt
-
-# node-waf configuration
-.lock-wscript
-
-# Compiled binary addons (http://nodejs.org/api/addons.html)
-build/Release
-
-# build folder for automated releases
-latest
-
-# Dependency directory
-# https://www.npmjs.org/doc/misc/npm-faq.html#should-i-check-my-node_modules-folder-into-git
-node_modules
-
-# Emacs
-*~
-
-# WebStorm/IntelliJ
-.idea
-
-# visual studio code
-.vscode
-
-# Babel.js
-lib/
-# types/* once we have full typescript support, we can generate types from the typescript files
-!types/tsconfig.json
-
-# cache folder
-.cache
-.eslintcache
-
-# Mac DS_Store files
-.DS_Store
-
-# Folder created by FileSystemAdapter
-/files
-
-# Redis Dump
-dump.rdb
-
-# AI agents
-.claude

.madgerc

@@ -1,10 +0,0 @@
-{
-	"detectiveOptions": {
-		"ts": {
-			"skipTypeImports": true
-		},
-    "es6": {
-			"skipTypeImports": true
-		}
-	}
-}

.npmignore

@@ -1,2 +0,0 @@
-types/tests.ts
-types/eslint.config.mjs

.nvmrc

@@ -1 +0,0 @@
-20.15.0

.nycrc

@@ -1,10 +0,0 @@
-{
-  "reporter": [
-    "lcov",
-    "text-summary"
-  ],
-  "exclude": [
-    "**/spec/**"
-  ]
-}
-

.prettierrc

@@ -1,5 +0,0 @@
-semi: true
-trailingComma: "es5"
-singleQuote: true
-arrowParens: "avoid"
-printWidth: 100

.releaserc.js

@@ -1,130 +0,0 @@
-/**
- * Semantic Release Config
- */
-
-const { readFile } = require('fs').promises;
-const { resolve } = require('path');
-
-// For ES6 modules use:
-// import { readFile } from 'fs/promises';
-// import { resolve, dirname } from 'path';
-// import { fileURLToPath } from 'url';
-
-// Get env vars
-const ref = process.env.GITHUB_REF;
-const serverUrl = process.env.GITHUB_SERVER_URL;
-const repository = process.env.GITHUB_REPOSITORY;
-const repositoryUrl = serverUrl + '/' + repository;
-
-// Declare params
-const resourcePath = './.releaserc/';
-const templates = {
-  main: { file: 'template.hbs', text: undefined },
-  header: { file: 'header.hbs', text: undefined },
-  commit: { file: 'commit.hbs', text: undefined },
-  footer: { file: 'footer.hbs', text: undefined },
-};
-
-// Declare semantic config
-async function config() {
-
-  // Get branch
-  const branch = ref?.split('/')?.pop()?.split('-')[0] || '(current branch could not be determined)';
-  // eslint-disable-next-line no-console
-  console.log(`Running on branch: ${branch}`);
-
-  // Set changelog file
-  const changelogFile = `./changelogs/CHANGELOG_release.md`;
-  // eslint-disable-next-line no-console
-  console.log(`Changelog file output to: ${changelogFile}`);
-
-  // Load template file contents
-  await loadTemplates();
-
-  const config = {
-    branches: [
-      'release',
-      { name: 'alpha', prerelease: true },
-      // { name: 'beta', prerelease: true },
-      // Long-Term-Support branch
-      { name: 'release-8.x.x', range: '8.x.x', channel: '8.x.x' },
-    ],
-    dryRun: false,
-    debug: true,
-    ci: true,
-    tagFormat: '${version}',
-    plugins: [
-      ['@semantic-release/commit-analyzer', {
-        preset: 'angular',
-        releaseRules: [
-          { type: 'docs', scope: 'README', release: 'patch' },
-          { scope: 'no-release', release: false },
-        ],
-        parserOpts: {
-          noteKeywords: ['BREAKING CHANGE'],
-        },
-      }],
-      ['@semantic-release/release-notes-generator', {
-        preset: 'angular',
-        parserOpts: {
-          noteKeywords: ['BREAKING CHANGE']
-        },
-        writerOpts: {
-          commitsSort: ['subject', 'scope'],
-          mainTemplate: templates.main.text,
-          headerPartial: templates.header.text,
-          commitPartial: templates.commit.text,
-          footerPartial: templates.footer.text,
-        },
-      }],
-      ['@semantic-release/changelog', {
-        'changelogFile': changelogFile,
-      }],
-      ['@semantic-release/npm', {
-        'npmPublish': true,
-      }],
-      ['@semantic-release/git', {
-        assets: [changelogFile, 'package.json', 'package-lock.json', 'npm-shrinkwrap.json'],
-      }],
-      ['@semantic-release/github', {
-        successComment: getReleaseComment(),
-        labels: ['type:ci'],
-        releasedLabels: ['state:released<%= nextRelease.channel ? `-\${nextRelease.channel}` : "" %>']
-      }],
-      // Back-merge module runs last because if it fails it should not impede the release process
-      [
-        "@saithodev/semantic-release-backmerge",
-        {
-          "backmergeBranches": [
-            // { from: 'beta', to: 'alpha' },
-            // { from: 'release', to: 'beta' },
-            { from: 'release', to: 'alpha' },
-          ]
-        }
-      ],
-    ],
-  };
-
-  return config;
-}
-
-async function loadTemplates() {
-  for (const template of Object.keys(templates)) {
-
-    // For ES6 modules use:
-    // const fileUrl = import.meta.url;
-    // const __dirname = dirname(fileURLToPath(fileUrl));
-
-    const filePath = resolve(__dirname, resourcePath, templates[template].file);
-    const text = await readFile(filePath, 'utf-8');
-    templates[template].text = text;
-  }
-}
-
-function getReleaseComment() {
-  const url = repositoryUrl + '/releases/tag/${nextRelease.gitTag}';
-  const comment = '🎉 This change has been released in version [${nextRelease.version}](' + url + ')';
-  return comment;
-}
-
-module.exports = config();

.releaserc/commit.hbs

@@ -1,61 +0,0 @@
-*{{#if scope}} **{{scope}}:**
-{{~/if}} {{#if subject}}
-  {{~subject}}
-{{~else}}
-  {{~header}}
-{{~/if}}
-
-{{~!-- commit link --}} {{#if @root.linkReferences~}}
-  ([{{shortHash}}](
-  {{~#if @root.repository}}
-    {{~#if @root.host}}
-      {{~@root.host}}/
-    {{~/if}}
-    {{~#if @root.owner}}
-      {{~@root.owner}}/
-    {{~/if}}
-    {{~@root.repository}}
-  {{~else}}
-    {{~@root.repoUrl}}
-  {{~/if}}/
-  {{~@root.commit}}/{{hash}}))
-{{~else}}
-  {{~shortHash}}
-{{~/if}}
-
-{{~!-- commit references --}}
-{{~#if references~}}
-  , closes
-  {{~#each references}} {{#if @root.linkReferences~}}
-    [
-    {{~#if this.owner}}
-      {{~this.owner}}/
-    {{~/if}}
-    {{~this.repository}}#{{this.issue}}](
-    {{~#if @root.repository}}
-      {{~#if @root.host}}
-        {{~@root.host}}/
-      {{~/if}}
-      {{~#if this.repository}}
-        {{~#if this.owner}}
-          {{~this.owner}}/
-        {{~/if}}
-        {{~this.repository}}
-      {{~else}}
-        {{~#if @root.owner}}
-          {{~@root.owner}}/
-        {{~/if}}
-          {{~@root.repository}}
-        {{~/if}}
-    {{~else}}
-      {{~@root.repoUrl}}
-    {{~/if}}/
-    {{~@root.issue}}/{{this.issue}})
-  {{~else}}
-    {{~#if this.owner}}
-      {{~this.owner}}/
-    {{~/if}}
-    {{~this.repository}}#{{this.issue}}
-  {{~/if}}{{/each}}
-{{~/if}}
-

.releaserc/footer.hbs

@@ -1,11 +0,0 @@
-{{#if noteGroups}}
-{{#each noteGroups}}
-
-### {{title}}
-
-{{#each notes}}
-* {{#if commit.scope}}**{{commit.scope}}:** {{/if}}{{text}} ([{{commit.shortHash}}]({{commit.shortHash}}))
-{{/each}}
-{{/each}}
-
-{{/if}}

.releaserc/header.hbs

@@ -1,25 +0,0 @@
-{{#if isPatch~}}
-  ##
-{{~else~}}
-  #
-{{~/if}} {{#if @root.linkCompare~}}
-  [{{version}}](
-  {{~#if @root.repository~}}
-    {{~#if @root.host}}
-      {{~@root.host}}/
-    {{~/if}}
-    {{~#if @root.owner}}
-      {{~@root.owner}}/
-    {{~/if}}
-    {{~@root.repository}}
-  {{~else}}
-    {{~@root.repoUrl}}
-  {{~/if~}}
-  /compare/{{previousTag}}...{{currentTag}})
-{{~else}}
-  {{~version}}
-{{~/if}}
-{{~#if title}} "{{title}}"
-{{~/if}}
-{{~#if date}} ({{date}})
-{{/if}}

.releaserc/template.hbs

@@ -1,14 +0,0 @@
-{{> header}}
-
-{{#each commitGroups}}
-
-{{#if title}}
-### {{title}}
-
-{{/if}}
-{{#each commits}}
-{{> commit root=@root}}
-{{/each}}
-{{/each}}
-
-{{> footer}}

6.0.0.md

@@ -1,78 +0,0 @@
-# Parse Server 6 Migration Guide <!-- omit in toc -->
-
-This document only highlights specific changes that require a longer explanation. For a full list of changes in Parse Server 6 please refer to the [changelog](https://github.com/parse-community/parse-server/blob/alpha/CHANGELOG.md).
-
----
-
-- [Incompatible git protocol with Node 14](#incompatible-git-protocol-with-node-14)
-- [Import Statement](#import-statement)
-- [Asynchronous Initialization](#asynchronous-initialization)
-
----
-
-## Incompatible git protocol with Node 14
-
-Parse Server 6 uses the Node Package Manger (npm) package lock file version 2. While version 2 is supposed to be backwards compatible with version 1, you may still encounter errors due to incompatible git protocols that cannot be interpreted correctly by npm bundled with Node 14.
-
-If you are encountering issues installing Parse Server on Node 14 because of dependency references in the package lock file using the `ssh` protocol, configure git to use the `https` protocol instead:
-
-```
-sudo git config --system url."https://github".insteadOf "ssh://git@github"
-```
-
-Alternatively you could manually replace the dependency URLs in the package lock file.
-
-⚠️ You could also delete the package lock file and recreate it with Node 14. Keep in mind that doing so you are not using an official version of Parse Server anymore. You may be using dependencies that have not been tested as part of the Parse Server release process.
-
-## Import Statement
-
-The import and initialization syntax has been simplified with more intuitive naming and structure.
-
-*Parse Server 5:*
-```js
-// Returns a Parse Server instance
-const ParseServer = require('parse-server');
-
-// Returns a Parse Server express middleware
-const { ParseServer } = require('parse-server');
-```
-
-*Parse Server 6:*
-```js
-// Both return a Parse Server instance
-const ParseServer = require('parse-server');
-const { ParseServer } = require('parse-server');
-```
-
-To get the express middleware in Parse Server 6, configure the Parse Server instance, start Parse Server and use its `app` property. See [Asynchronous Initialization](#asynchronous-initialization) for more details.
-
-## Asynchronous Initialization
-
-Previously, it was possible to mount Parse Server before it was fully started up and ready to receive requests. This could result in undefined behavior, such as Parse Objects could be saved before Cloud Code was registered. To prevent this, Parse Server 6 requires to be started asynchronously before being mounted.
-
-*Parse Server 5:*
-```js
-// 1. Import Parse Server
-const { ParseServer } = require('parse-server');
-
-// 2. Create a Parse Server instance as express middleware
-const server = new ParseServer(config);
-
-// 3. Mount express middleware
-app.use("/parse", server);
-```
-
-*Parse Server 6:*
-```js
-// 1. Import Parse Server
-const ParseServer = require('parse-server');
-
-// 2. Create a Parse Server instance
-const server = new ParseServer(config);
-
-// 3. Start up Parse Server asynchronously
-await server.start();
-
-// 4. Mount express middleware
-app.use("/parse", server.app);
-```

8.0.0.md

@@ -1,44 +0,0 @@
-# Parse Server 8 Migration Guide <!-- omit in toc -->
-
-This document only highlights specific changes that require a longer explanation. For a full list of changes in Parse Server 8 please refer to the [changelog](https://github.com/parse-community/parse-server/blob/alpha/CHANGELOG.md).
-
----
-
-- [Email Verification](#email-verification)
-- [Database Indexes](#database-indexes)
-
----
-
-## Email Verification
-
-In order to remove sensitive information (PII) from technical logs, the `Parse.User.username` field has been removed from the email verification process. This means the username will no longer be used and the already existing verification token, that is internal to Parse Server and associated with the user, will be used instead. This makes use of the fact that an expired verification token is not deleted from the database by Parse Server, despite being expired, and can therefore be used to identify a user.
-
-This change affects how verification emails with expired tokens are handled. When opening a verification link that contains an expired token, the page that the user is redirected to will no longer provide the `username` as a URL query parameter. Instead, the URL query parameter `token` will be provided.
-
-The request to re-send a verification email changed to sending a `POST` request to the endpoint `/resend_verification_email` with `token` in the body, instead of `username`. If you have customized the HTML pages for email verification either for the `PagesRouter` in `/public/` or the deprecated `PublicAPIRouter` in `/public_html/`, you need to adapt the form request in your custom pages. See the example pages in these aforementioned directories for how the forms must be set up.
-
-> [!WARNING]
-> An expired verification token is not automatically deleted from the database by Parse Server even though it has expired. If you have implemented a custom clean-up logic that removes expired tokens, this will break the form request to re-send a verification email as the expired token won't be found and cannot be associated with any user. In that case you'll have to implement your custom process to re-send a verification email.
-
-> [!IMPORTANT]
-> Parse Server does not keep a history of verification tokens but only stores the most recently generated verification token in the database. Every time Parse Server generates a new verification token, the currently stored token is replaced. If a user opens a link with an expired token, and that token has already been replaced in the database, Parse Server cannot associate the expired token with any user. In this case, another way has to be offered to the user to re-send a verification email. To mitigate this issue, set the Parse Server option `emailVerifyTokenReuseIfValid: true` and set `emailVerifyTokenValidityDuration` to a longer duration, which ensures that the currently stored verification token is not replaced too soon.
-
-Related pull request:
-
-- https://github.com/parse-community/parse-server/pull/8488
-
-## Database Indexes
-
-As part of the email verification and password reset improvements in Parse Server 8, the queries used for these operations have changed to use tokens instead of username/email fields. To ensure optimal query performance, Parse Server now automatically creates indexes on the following fields during server initialization:
-
-- `_User._email_verify_token`: used for email verification queries
-- `_User._perishable_token`: used for password reset queries
-
-These indexes are created automatically when Parse Server starts, similar to how indexes for `username` and `email` fields are created. No manual intervention is required.
-
-> [!WARNING]
-> If you have a large existing user base, the index creation may take some time during the first server startup after upgrading to Parse Server 8. The server logs will indicate when index creation is complete or if any errors occur. If you have any concerns regarding a potential database performance impact during index creation, you could create these indexes manually in a controlled procedure before upgrading Parse Server.
-
-Related pull request:
-
-- https://github.com/parse-community/parse-server/pull/9893

CHANGELOG.md

@@ -1,37 +0,0 @@
-# Changelog
-
-Changelogs are separated by release type for better overview.
-
-## ✅ [Stable Releases][log_release]
-
-> ### “Stable for production!”
-
-These are the official, stable releases that you can use in your production environments.
-
-Details:
-- Stability: *stable*
-- NPM channel: `@latest`
-- Branch: [release][branch_release]
-- Purpose: official release
-- Suitable environment: production
-
-## 🔥 [Alpha Releases][log_alpha]
-
-> ### “If you are curious to see what's next!”
-
-These releases contain the latest development changes, but you should be prepared for anything, including sudden breaking changes or code refactoring. Use this branch to contribute to the project and open pull requests.
-
-Details:
-- Stability: *unstable*
-- NPM channel: `@alpha`
-- Branch: [alpha][branch_alpha]
-- Purpose: product development
-- Suitable environment: experimental
-
-
-[log_release]: https://github.com/parse-community/parse-server/blob/release/changelogs/CHANGELOG_release.md
-[log_beta]: https://github.com/parse-community/parse-server/blob/beta/changelogs/CHANGELOG_beta.md
-[log_alpha]: https://github.com/parse-community/parse-server/blob/alpha/changelogs/CHANGELOG_alpha.md
-[branch_release]: https://github.com/parse-community/parse-server/tree/release
-[branch_beta]: https://github.com/parse-community/parse-server/tree/beta
-[branch_alpha]: https://github.com/parse-community/parse-server/tree/alpha

CODE_OF_CONDUCT.md

@@ -1,46 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at codeofconduct@parseplatform.org. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -1,695 +0,0 @@
-# Contributing to Parse Server <!-- omit in toc -->
-
-## Table of Contents <!-- omit in toc -->
-- [Contributing](#contributing)
-  - [Issue vs. Pull Request](#issue-vs-pull-request)
-  - [Scope](#scope)
-  - [Templates](#templates)
-- [Why Contributing?](#why-contributing)
-- [Contribution FAQs](#contribution-faqs)
-  - [Reviewer Role](#reviewer-role)
-  - [Review Feedback](#review-feedback)
-  - [Merge Readiness](#merge-readiness)
-  - [Review Validity](#review-validity)
-  - [Code Ownership](#code-ownership)
-  - [Access Permissions](#access-permissions)
-  - [New Private Repository](#new-private-repository)
-  - [New Public Repository](#new-public-repository)
-- [Environment Setup](#environment-setup)
-  - [Recommended Tools](#recommended-tools)
-  - [Setting up your local machine](#setting-up-your-local-machine)
-  - [Good to Know](#good-to-know)
-  - [Troubleshooting](#troubleshooting)
-  - [Please Do's](#please-dos)
-    - [TypeScript Tests](#typescript-tests)
-  - [Test against Postgres](#test-against-postgres)
-    - [Postgres with Docker](#postgres-with-docker)
-  - [Performance Testing](#performance-testing)
-    - [Adding Tests](#adding-tests)
-    - [Adding Benchmarks](#adding-benchmarks)
-    - [Benchmark Guidelines](#benchmark-guidelines)
-- [Breaking Changes](#breaking-changes)
-  - [Deprecation Policy](#deprecation-policy)
-- [Feature Considerations](#feature-considerations)
-  - [Security Checks](#security-checks)
-    - [Add Security Check](#add-security-check)
-    - [Wording Guideline](#wording-guideline)
-  - [Parse Error](#parse-error)
-  - [Parse Server Configuration](#parse-server-configuration)
-- [Pull Request](#pull-request)
-  - [Commit Message](#commit-message)
-  - [Breaking Change](#breaking-change)
-- [Merging](#merging)
-  - [Breaking Change](#breaking-change-1)
-  - [Reverting](#reverting)
-  - [Security Vulnerability](#security-vulnerability)
-    - [Local Testing](#local-testing)
-    - [Environment](#environment)
-    - [Merging](#merging-1)
-- [Releasing](#releasing)
-  - [General Considerations](#general-considerations)
-  - [Major Release / Long-Term-Support](#major-release--long-term-support)
-  - [Preparing Release](#preparing-release)
-  - [Publishing Release (forward-merge):](#publishing-release-forward-merge)
-  - [Publishing Hotfix (back-merge):](#publishing-hotfix-back-merge)
-  - [Publishing Major Release (Yearly Release)](#publishing-major-release-yearly-release)
-- [Versioning](#versioning)
-- [Code of Conduct](#code-of-conduct)
-
-## Contributing
-
-Before you start to code, please open a [new issue](https://github.com/parse-community/parse-server/issues/new/choose) to describe your idea, or search for and continue the discussion in an [existing issue](https://github.com/parse-community/parse-server/issues).
-
-> ⚠️ Please do not post a security vulnerability on GitHub or in the Parse Community Forum. Instead, follow the [Parse Community Security Policy](https://github.com/parse-community/parse-server/security/policy).
-
-Please completely fill out any templates to provide essential information about your new feature or the bug you discovered.
-
-Together we will plan out the best conceptual approach for your contribution, so that your and our time is invested in the best possible approach. The discussion often reveals how to leverage existing features of Parse Server to reach your goal with even less effort and in a more sustainable way.
-
-When you are ready to code, you can find more information about opening a pull request in the [GitHub docs](https://help.github.com/articles/creating-a-pull-request/).
-
-Whether this is your first contribution or you are already an experienced contributor, the Parse Community has your back – don't hesitate to ask for help!
-
-### Issue vs. Pull Request
-
-An issue is required to be linked in every pull request. We understand that no-one likes to create an issue for something that appears to be a simple pull request, but here is why this is beneficial for everyone:
-
-- An issue get more visibility than a pull request as issues can be pinned, receive bounties and it is primarily the issue list that people browse through rather than the more technical pull request list. Visibility is a key aspect so others can weigh in on issues and contribute their opinion.
-- The discussion in the issue is different from the discussion in the pull request. The issue discussion is focused on the issue and how to address it, whereas the discussion in the pull request is focused on a specific implemention. An issue may even have multiple pull requests because either the issue requires multiple implementations or multiple pull requests are opened to compare and test different approaches to later decide for one.
-- High-level conceptual discussions about the issue should be still available, even if a pull request is closed because its appraoch was discarded. If these discussions are in the pull request instead, they can easily become fragmented over multiple pull requests and issues, which can make it very hard to make sense of all aspects of an issue.
-
-### Scope
-
-An issue and pull request must limit its scope on a distinct issue. Pull requests can only contain changes that are required to address the scoped issue. While it may seem quick and easy to add unrelated changes to the pull request, it can cause singificant complications after merging. Some of the reasons are:
-
-- A pull request corresponds to a single changelog entry. A changelog entry should not describe multiple unrelated changes in one entry for better readability.
-- A pull request creates a distinct commit; having an individual commit for each limited scope makes it easier for others to go back in the commit history and debug. Bugs are generally more difficult to identify and fix if there are various unrelated changes merged at once.
-- If a pull request needs to be reverted, unrelated changes will be reverted as well. That makes it more complex and time consuming to revert, having to consider its effects and possibly publishing a broken release or requiring a follow-up pull request with code manipulation.
-
-### Templates
-
-You are required to use and completely fill out the templates for new issues and pull requests. We understand that no-one enjoys filling out forms, but here is why this is beneficial for everyone:
-
-- It may take you 30 seconds longer, but will save even more time for everyone else trying to understand your issue.
-- It helps to fix issues and merge pull requests faster as reviewers spend less time trying to understand your issue.
-- It makes investigations easier when others try to understand your issue and code changes made even years later.
-
-## Why Contributing?
-
-Buy cheap, buy twice. What? No, this is not the Economics 101 class, but the same is true for contributing.
-
-There are two ways of writing a feature or fixing a bug. Sometimes the quick solution is to just write a Cloud Code function that does what you want. Contributing by making the change directly in Parse Server may take a bit longer, but it actually saves you much more time in the long run.
-
-Consider the benefits you get:
-
-- #### 🚀 Higher efficiency
-  Your code is examined for efficiency and interoperability with existing features by the community.
-- #### 🛡 Stronger security
-  Your code is scrutinized for bugs and vulnerabilities and automated checks help to identify security issues that may arise in the future.
-- #### 🧬 Continuous improvement
-  If your feature is used by others it is likely to be continuously improved and extended by the community.
-- #### 💝 Giving back
-  You give back to the community that contributed to make the Parse Platform become what it is today and for future developers to come.
-- #### 🧑‍🎓 Improving yourself
-  You learn to better understand the inner workings of Parse Server, which will help you to write more efficient and resilient code for your own application.
-
-Most importantly, with every contribution you improve your skills so that future contributions take even less time and you get all the benefits above for free — easy choice, right?
-
-## Contribution FAQs
-
-### Reviewer Role
-
-> *Instead of writing review comments back-and-forth, why doesn't the reviewer just write the code themselves?*
-
-A reviewer is already helping you to make a code contribution through their review. A reviewer *may* even help you to write code by actually writing it for you, but is not obliged to do so.
-
-GitHub allows reviewers to suggest and write code changes as part of the review feedback. These code suggestions are likely to contain mistakes due to the lack of code syntax checks when writing code directly on GitHub. You should therefore always review these suggestions before accepting them, ideally in an IDE. If you merge a code suggestion and the CI then fails, take another look at the code change before asking the reviewer for help.
-
-### Review Feedback
-
-> *It takes too much effort to incorporate the review feedback, why why can't you just merge my pull request?*
-
-If you are a new contributor, it's naturally a learning experience for you and therefore takes longer. We welcome contributors of any experience levels and gladly support you in getting familiar with the code base and our quality standards and contribution requirements. In return we expect you to be open to and appreciative of the reviewers' feedback.
-
-In a large pull request, it can be a significant effort to bring it over the finish line. Luckily this is a collaborative environment and others are free to jump in to contribute to the pull request to share the effort. You can either give others access to your fork or they can open their own pull request based on your previous work.
-
-If you are out of resources stay calm, explain your personal constraints (expertise or time) and ask for help. Wasting time by complaining about the amount of review comments will neither use your own time in a meaningful way, nor the time of others who read your complaint.
-
-This is a collaborative enviroment in which everyone works on a common goal - to get a pull request ready for merging. Reviewers are working *with* you to get your pull request ready, *not against you*.
-
-**❗️ Always be mindful that the reviewers' efforts are an integral part of code contribution. Their review is as important as your written code and their review time is a valuable as your coding time.**
-
-### Merge Readiness
-
-> *The feature already works, why do you request more changes instead of just merging my pull request?*
-
-A feature may work for your own use case or in your own environment, but that doesn't necessarily mean that it's ready for merging. Aside from code quality and code style requirements, reviewers also review based on strategic and architectural considerations. It's often easy to just get a feature to work, but it needs to be also maintained in the future, robust therefore well tested and validated, intuitive for other developers to use, well documented, and not cause a forseeable breaking change in the near future.
-
-### Review Validity
-
-> *The reviewer has never worked on the issue and was never part of any previous discussion, why would I care about their opinion?*
-
-It's contrary to an open, collaborative environment to expect others to be involved in an issue or discussion since its beginning. Such a mindset would close out any new views, which are important for a differentiated discussion.
-
-> *The reviewer doesn't have any expertise in that matter, why would I care about their opinion?*
-
-Your arguments must focus on the issue, not on your assumption of someone else's personal experience. We will take immediate and appropriate action in case of personal attacks, regardless of your previous contributions. Personal attacks are not permissible. If you became a victim of personal attacks, you can privately [report](https://docs.github.com/en/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) the GitHub comment to the Parse Platform PMC.
-
-### Code Ownership
-
-> *Can I open a new pull request based on another author's pull request?*
-
-If your pull request contains work from someone else then you are required to get their permission to use their work in your pull request. Please make sure to observe the [license](LICENSE) for more details. In addition, as an appreciative gesture you should clearly mention that your pull request is based on another pull request with a link in the top-most comment of your pull request. To avoid this issue we encourage contributors to collaborate on a single pull request to preserve the commit history and clearly identify each author's contribution. To do so, you can review the other author's pull request and submit your code suggestions, or ask the original author to grant you write access to their repository to also be able to make commits directly to their pull request.
-
-### Access Permissions
-
-> *Can I get write access to the repository to make changes faster?*
-
-Keeping our products safe and secure is one of your top priorities. Our security policy mandates that write access to repositories is only provided to as few people as necessary. All usual contributions can be made via public pull requests. If you think you need write access, contact the repository team and explain in detail what the constraint is that you are trying to overcome. We want to make contributing for you as easy as possible. If there are any bottlenecks that are slowing you down we are happy to receive your feedback to see where we can improve.
-
-### New Private Repository
-
-> *Can I get a new private repository within the Parse Platform organization to work on some stuff?*
-
-Private repositories are not provided unless there is a significant constraint or requirement that makes it necessary. For example, when collaborating on fixing a security vulnerability we provide private repositories to allow collaborators to share sensitive information within a select group.
-
-### New Public Repository
-
-> *Can I get a new public repository within the Parse Platform organization to work on some stuff?*
-
-First of all, we appreciate your contribution. In rare cases, where we consider it beneficial to the advancement of the repository, a new public repository for a specific purpose may be provided, for example for increased visibility or to provide the organization's GitHub ressources. In other cases, we encourage you to start your contribution in a personal repository of your own GitHub account, and later transfer it to the Parse Platform organization. We will be happy to assist you in the repository transfer.
-
-## Environment Setup
-
-### Recommended Tools
-
-* [Visual Studio Code](https://code.visualstudio.com), the popular IDE.
-* [Jasmine Test Explorer](https://marketplace.visualstudio.com/items?itemName=hbenl.vscode-jasmine-test-adapter), a very practical test exploration plugin which let you run, debug and see the test results inline.
-
-### Setting up your local machine
-
-* [Fork](https://github.com/parse-community/parse-server) this project and clone the fork on your local machine:
-
-```sh
-$ git clone https://github.com/parse-community/parse-server
-$ cd parse-server # go into the clone directory
-$ npm install # install all the node dependencies
-$ code . # launch vscode
-$ npm run watch # run babel watching for local file changes
-```
-
-> To launch VS Code from the terminal with the `code` command you first need to follow the [launching from the command line section](https://code.visualstudio.com/docs/setup/mac#_launching-from-the-command-line) in the VS Code setup documentation.
-
-Once you have babel running in watch mode, you can start making changes to parse-server.
-
-### Good to Know
-
-* The `lib/` folder is not committed, so never make changes in there.
-* Always make changes to files in the `src/` folder.
-* All the tests should point to sources in the `lib/` folder.
-* The `lib/` folder is produced by `babel` using either the `npm run build`, `npm run watch`, or the `npm run prepare` step.
-* The `npm run prepare` step is automatically invoked when your package depends on forked parse-server installed via git for example using `npm install --save git+https://github.com/[username]/parse-server#[branch/commit]`.
-* The tests are run against a single server instance. You can change the server configurations using `await reconfigureServer({ ... some configuration })` found in `spec/helper.js`.
-* The tests are ran at random.
-* Caches and Configurations are reset after every test.
-* Users are logged out after every test.
-* Cloud Code hooks are removed after every test.
-* Database is deleted after every test (indexes are not removed for speed)
-* Tests are located in the `spec` folder
-* For better test reporting enable `PARSE_SERVER_LOG_LEVEL=debug`
-
-### Troubleshooting
-
-*Question*: I modify the code in the src folder but it doesn't seem to have any effect.<br/>
-*Answer*: Check that `npm run watch` is running
-
-*Question*: How do I use breakpoints and debug step by step?<br/>
-*Answer*: The easiest way is to install [Jasmine Test Explorer](https://marketplace.visualstudio.com/items?itemName=hbenl.vscode-test-explorer), it will let you run selectively tests and debug them.
-
-*Question*: How do I deploy my forked version on my servers?<br/>
-*Answer*: In your `package.json`, update the `parse-server` dependency to `https://github.com/[username]/parse-server#[branch/commit]`. Run `npm install`, commit the changes and deploy to your servers.
-
-*Question*: How do I deploy my forked version using docker?<br/>
-*Answer*: In your `package.json`, update the `parse-server` dependency to `https://github.com/[username]/parse-server#[branch/commit]`. Make sure the `npm install` step in your `Dockerfile` is running under non-privileged user for the ``npm run prepare`` step to work correctly. For official node images from hub.docker.com that non-privileged user is `node` with `/home/node` working directory.
-
-
-### Please Do's
-
-* Begin by reading the [Development Guide](http://docs.parseplatform.org/parse-server/guide/#development-guide) to learn how to get started running the parse-server.
-* Take testing seriously! Aim to increase the test coverage with every pull request. To obtain the test coverage of the project, run: `npm run coverage`
-* Run the tests for the file you are working on with the following command: `npm test spec/MyFile.spec.js`
-* Run the tests for the whole project to make sure the code passes all tests. This can be done by running the test command for a single file but removing the test file argument. The results can be seen at *<PROJECT_ROOT>/coverage/lcov-report/index.html*.
-* Lint your code by running `npm run lint` to make sure the code is not going to be rejected by the CI.
-* **Do not** publish the *lib* folder.
-* Mocks belong in the `spec/support` folder.
-* Please consider if any changes to the [docs](http://docs.parseplatform.org) are needed or add additional sections in the case of an enhancement or feature.
-
-#### TypeScript Tests
-
-Type tests are located in [/types/tests.ts](/types/tests.ts) and are responsible for ensuring that the type generation for each class is behaving as expected. Types are generated by manually running the script `npm run build:types`. The generated types are `.d.ts` files located in [/types](/types) and must not be manually changed after generation.
-
-> [!CAUTION]
-> An exemption are type changes to `src/Options/index.js` which must be manually updated in `types/Options/index.d.ts`, as these types are not generated via a script.
-
-When developing type definitions you can run `npm run watch:ts` in order to rebuild your changes automatically upon each save. Use `npm run test:types` in order to run types tests against generated `.d.ts` files.
-
-### Test against Postgres
-
-If your pull request introduces a change that may affect the storage or retrieval of objects, you may want to make sure it plays nice with Postgres.
-
-* You'll need to have postgres running on your machine and setup [appropriately](https://github.com/parse-community/parse-server/blob/master/scripts/before_script_postgres.sh) or use [`Docker`](#postgres-with-docker)
-* Run the tests against the postgres database with:
-  ```
-  PARSE_SERVER_TEST_DB=postgres PARSE_SERVER_TEST_DATABASE_URI=postgres://postgres:password@localhost:5432/parse_server_postgres_adapter_test_database npm run testonly
-  ``` 
-* The Postgres adapter has a special debugger that traces all the sql commands. You can enable it with setting the environment variable `PARSE_SERVER_LOG_LEVEL=debug`
-* If your feature is intended to only work with MongoDB, you should disable PostgreSQL-specific tests with:
-
-  - `describe_only_db('mongo')` // will create a `describe` that runs only on mongoDB
-  - `it_only_db('mongo')` // will make a test that only runs on mongo
-  - `it_exclude_dbs(['postgres'])` // will make a test that runs against all DB's but postgres
-* Similarly, if your feature is intended to only work with PostgreSQL, you should disable MongoDB-specific tests with:
- 
-  - `describe_only_db('postgres')` // will create a `describe` that runs only on postgres
-  - `it_only_db('postgres')` // will make a test that only runs on postgres
-  - `it_exclude_dbs(['mongo'])` // will make a test that runs against all DB's but mongo
-
-* If your feature is intended to work with MongoDB and PostgreSQL, you can include or exclude tests more granularly with:
-
-  - `it_only_mongodb_version('>=4.4')` // will test with any version of Postgres but only with version >=4.4 of MongoDB; accepts semver notation to specify a version range
-  - `it_only_postgres_version('>=13')` // will test with any version of Mongo but only with version >=13 of Postgres; accepts semver notation to specify a version range
-
-#### Postgres with Docker
-
-[PostGIS images (select one with v2.2 or higher) on docker hub](https://hub.docker.com/r/postgis/postgis) is based off of the official [postgres](https://hub.docker.com/_/postgres) image and will work out-of-the-box (as long as you create a user with the necessary extensions for each of your Parse databases; see below). To launch the compatible Postgres instance, copy and paste the following line into your shell:
-
-```
-docker run -d --name parse-postgres -p 5432:5432 -e POSTGRES_PASSWORD=password --rm postgis/postgis:17-3.5-alpine && sleep 20 && docker exec -it parse-postgres psql -U postgres -c 'CREATE DATABASE parse_server_postgres_adapter_test_database;' && docker exec -it parse-postgres psql -U postgres -c 'CREATE EXTENSION pgcrypto; CREATE EXTENSION postgis;' -d parse_server_postgres_adapter_test_database && docker exec -it parse-postgres psql -U postgres -c 'CREATE EXTENSION postgis_topology;' -d parse_server_postgres_adapter_test_database
-```
-To stop the Postgres instance:
-
-```
-docker stop parse-postgres
-```
-
-You can also use the [postgis/postgis:17-3.5-alpine](https://hub.docker.com/r/postgis/postgis) image in a Dockerfile and copy this [script](https://github.com/parse-community/parse-server/blob/master/scripts/before_script_postgres.sh) to the image by adding the following lines:
-
-```
-#Install additional scripts. These are run in abc order during initial start
-COPY ./scripts/setup-dbs.sh /docker-entrypoint-initdb.d/setup-dbs.sh
-RUN chmod +x /docker-entrypoint-initdb.d/setup-dbs.sh
-```
-
-Note that the script above will ONLY be executed during initialization of the container with no data in the database, see the official [Postgres image](https://hub.docker.com/_/postgres) for details. If you want to use the script to run again be sure there is no data in the /var/lib/postgresql/data of the container.
-
-### Performance Testing
-
-Parse Server includes an automated performance benchmarking system that runs on every pull request to detect performance regressions and track improvements over time.
-
-#### Adding Tests
-
-You should consider adding performance benchmarks if your contribution:
-
-- **Introduces a performance-critical feature**: Features that will be frequently used in production environments, such as new query operations, authentication methods, or data processing functions.
-- **Modifies existing critical paths**: Changes to core functionality like object CRUD operations, query execution, user authentication, file operations, or Cloud Code execution.
-- **Has potential performance impact**: Any change that affects database operations, network requests, data parsing, caching mechanisms, or algorithmic complexity.
-- **Optimizes performance**: If your PR specifically aims to improve performance, adding benchmarks helps verify the improvement and prevents future regressions.
-
-#### Adding Benchmarks
-
-Performance benchmarks are located in [`benchmark/performance.js`](benchmark/performance.js). To add a new benchmark:
-
-1. **Identify the operation to benchmark**: Determine the specific operation you want to measure (e.g., a new query type, a new API endpoint).
-
-2. **Create a benchmark function**: Follow the existing patterns in `benchmark/performance.js`:
-   ```javascript
-   async function benchmarkNewFeature() {
-     return measureOperation('Feature Name', async () => {
-       // Your operation to benchmark
-       const result = await someOperation();
-     }, ITERATIONS);
-   }
-   ```
-
-3. **Add to benchmark suite**: Register your benchmark in the `runBenchmarks()` function:
-   ```javascript
-   console.error('Running New Feature benchmark...');
-   await cleanupDatabase();
-   results.push(await benchmarkNewFeature());
-   ```
-
-4. **Test locally**: Run the benchmarks locally to verify they work:
-   ```bash
-   npm run benchmark:quick  # Quick test with 10 iterations
-   npm run benchmark        # Full test with 10,000 iterations
-   ```
-
-For new features where no baseline exists, the CI will establish new benchmarks that future PRs will be compared against.
-
-#### Benchmark Guidelines
-
-- **Keep benchmarks focused**: Each benchmark should test a single, well-defined operation.
-- **Use realistic data**: Test with data that reflects real-world usage patterns.
-- **Clean up between runs**: Use `cleanupDatabase()` to ensure consistent test conditions.
-- **Consider iteration count**: Use fewer iterations for expensive operations (see `ITERATIONS` environment variable).
-- **Document what you're testing**: Add clear comments explaining what the benchmark measures and why it's important.
-
-## Breaking Changes
-
-Breaking changes should be avoided whenever possible. For a breaking change to be accepted, the benefits of the change have to clearly outweigh the costs of developers having to adapt their deployments. If a breaking change is only cosmetic it will likely be rejected and preferred to become obsolete organically during the course of further development, unless it is required as part of a larger change. Breaking changes should follow the [Deprecation Policy](#deprecation-policy).
-
-Please consider that Parse Server is just one component in a stack that requires attention. A breaking change requires resources and effort to adapt an environment. An unnecessarily high frequency of breaking changes can have detrimental side effects such as:
-- "upgrade fatigue" where developers run old versions of Parse Server because they cannot always attend to every update that contains a breaking change
-- less secure Parse Server deployments that run on old versions which is contrary to the security evangelism Parse Server intends to facilitate for developers
-- less feedback and slower identification of bugs and an overall slow-down of Parse Server development because new versions with breaking changes also include new features we want to get feedback on
-
-### Deprecation Policy
-
-If you change or remove an existing feature that would lead to a breaking change, use the following deprecation pattern:
-  - Make the new feature or change optional, if necessary with a new Parse Server option parameter.
-  - Use a default value that falls back to existing behavior.
-  - Add a deprecation definition in `Deprecator/Deprecations.js` that will output a deprecation warning log message on Parse Server launch, for example:
-    > DeprecationWarning: The Parse Server option 'example' will be removed in a future release.
-
-For deprecations that can only be determined ad-hoc during runtime, for example Parse Query syntax deprecations, use the `Deprecator.logRuntimeDeprecation()` method.
-
-Deprecations become breaking changes after notifying developers through deprecation warnings for at least one entire previous major release. For example:
-  - `4.5.0` is the current version
-  - `4.6.0` adds a new optional feature and a deprecation warning for the existing feature
-  - `5.0.0` marks the beginning of logging the deprecation warning for one entire major release
-  - `6.0.0` makes the breaking change by removing the deprecation warning and making the new feature replace the existing feature
-
-See the [Deprecation Plan](https://github.com/parse-community/parse-server/blob/master/DEPRECATIONS.md) for an overview of deprecations and planned breaking changes.
-
-## Feature Considerations
-### Security Checks
-
-The Parse Server security checks feature warns developers about weak security settings in their Parse Server deployment.
-
-A security check needs to be added for every new feature or enhancement that allows the developer to configure it in a way that weakens security mechanisms or exposes functionality which creates a weak spot for malicious attacks. If you are not sure whether your feature or enhancements requires a security check, feel free to ask.
-
-For example, allowing public read and write to a class may be useful to simplify development but should be disallowed in a production environment.
-
-Security checks are added in [CheckGroups](https://github.com/parse-community/parse-server/tree/master/src/Security/CheckGroups).
-
-#### Add Security Check
-Adding a new security check for your feature is easy and fast:
-1. Look into [CheckGroups](https://github.com/parse-community/parse-server/tree/master/src/Security/CheckGroups) whether there is an existing `CheckGroup[Category].js` file for the category of check to add. For example, a check regarding the database connection is added to `CheckGroupDatabase.js`.
-2. If you did not find a file, duplicate an existing file and replace the category name in `setName()` and the checks in `setChecks()`:
-    ```js
-    class CheckGroupNewCategory extends CheckGroup {
-      setName() {
-        return 'House';
-      }
-      setChecks() {
-        return [
-          new Check({
-            title: 'Door locked',
-            warning: 'Anyone can enter your house.',
-            solution: 'Lock the door.',
-            check: () => {    
-              return;     // Example of a passing check
-            }
-          }),
-          new Check({
-            title: 'Camera online',
-            warning: 'Security camera is offline.',
-            solution: 'Check the camera.',
-            check: async () => {  
-              throw 1;     // Example of a failing check
-            }
-          }),
-        ];
-      }
-    }
-    ```
-
-3. If you added a new file in the previous step, reference the file in [CheckGroups.js](https://github.com/parse-community/parse-server/blob/master/src/Security/CheckGroups/CheckGroups.js), which is the collector of all security checks:
-    ```
-    export { default as CheckGroupNewCategory } from './CheckGroupNewCategory';
-    ```
-4. Add a test that covers the new check to [SecurityCheckGroups.js](https://github.com/parse-community/parse-server/blob/master/spec/SecurityCheckGroups.js) for the cases of success and failure.
-
-#### Wording Guideline
-Consider the following when adding a new security check:
-- *Group.name*: The category name; ends without period as this is a headline.
-- *Check.title*: Is the positive hypothesis that should be checked, for example "Door locked" instead of "Door unlocked"; ends without period as this is a title.
-- *Check.warning*: The warning if the test fails; ends with period as this is a description.
-- *Check.solution*: The recommended solution if the test fails; ends with period as this is an instruction.
-- The wordings must not contain any sensitive information such as keys, as the security report may be exposed in logs.
-- The wordings should be concise and not contain verbose explanations, for example "Door locked" instead of "Door has been locked securely".
-- Do not use pronouns such as "you" or "your" because log files can have various readers with different roles. Do not use pronouns such as "I" or "me" because although we love it dearly, Parse Server is not a human.
-
-### Parse Error
-
-Introducing new Parse Errors requires the following steps:
-
-1. Research whether an existing Parse Error already covers the error scenario. Keep in mind that reusing an already existing Parse Error does not allow to distinguish between scenarios in which the same error is thrown, so it may be necessary to add a new and more specific Parse Error, even though a more general Parse Error already exists.
-⚠️ Currently (as of Dec. 2020), there are inconsistencies between the Parse Errors documented in the Parse Guides, coded in the Parse JS SDK and coded in Parse Server, therefore research regarding the availability of error codes has to be conducted in all of these sources.
-1. Add the new Parse Error to [/src/ParseError.js](https://github.com/parse-community/Parse-SDK-JS/blob/master/src/ParseError.js) in the Parse JavaScript SDK. This is the primary reference for Parse Errors for the Parse JavaScript SDK and Parse Server.
-1. Create a pull request for the Parse JavaScript SDK including the new Parse Errors. The PR needs to be merged and a new Parse JS SDK version needs to be released.
-1. Change the Parse JS SDK dependency in [package.json](https://github.com/parse-community/parse-server/blob/master/package.json) of Parse Server to the newly released Parse JS SDK version, so that the new Parse Error is recognized by Parse Server.
-1. When throwing the new Parse Error in code, do not hard-code the error code but instead reference the error code from the Parse Error. For example:
-    ```javascript
-    throw new Parse.Error(Parse.Error.EXAMPLE_ERROR_CODE, 'Example error message.');
-    ```
-1. Choose a descriptive error message that provdes more details about the specific error scenario. Different error messages may be used for the same error code. For example:
-    ```javascript
-    throw new Parse.Error(Parse.Error.FILE_SAVE_ERROR, 'The file could not be saved because it exceeded the maximum allowed file size.');
-    throw new Parse.Error(Parse.Error.FILE_SAVE_ERROR, 'The file could not be saved because the file format was incorrect.');
-    ```
-1. Add the new Parse Error to the [docs](https://github.com/parse-community/docs/blob/gh-pages/_includes/common/errors.md).
-
-### Parse Server Configuration
-
-Introducing new [Parse Server configuration][config] parameters requires the following steps:
-
-1. Add parameters definitions in [/src/Options/index.js][config-index].
-2. If the new parameter does not have one single value but is a parameter group (an object containing multiple sub-parameters):
-   - add the environment variable prefix for the parameter group to `nestedOptionEnvPrefix` in [/resources/buildConfigDefinition.js](https://github.com/parse-community/parse-server/blob/master/resources/buildConfigDefinition.js)
-   - add the parameter group type to `nestedOptionTypes` in [/resources/buildConfigDefinition.js](https://github.com/parse-community/parse-server/blob/master/resources/buildConfigDefinition.js)
-  
-    For example, take a look at the existing Parse Server `security` parameter. It is a parameter group, because it has multiple sub-parameter such as `checkGroups`. Its interface is defined in [index.js][config-index] as `export interface SecurityOptions`. Therefore, the value to add to `nestedOptionTypes` would be `SecurityOptions`, the value to add to `nestedOptionEnvPrefix` would be `PARSE_SERVER_SECURITY_`.
-
-3. Execute `npm run definitions` to automatically create the definitions in [/src/Options/Definitions.js][config-def] and [/src/Options/docs.js][config-docs].
-4. Add parameter value validation in [/src/Config.js](https://github.com/parse-community/parse-server/blob/master/src/Config.js).
-5. Add test cases to ensure the correct parameter value validation. Parse Server throws an error at launch if an invalid value is set for any configuration parameter.
-6. Execute `npm run docs` to generate the documentation in the `/out` directory. Take a look at the documentation whether the description and formatting of the newly introduced parameters is satisfactory.
-
-## Pull Request
-
-### Commit Message
-
-For release automation, the title of pull requests needs to be written in a defined syntax. We loosely follow the [Conventional Commits](https://www.conventionalcommits.org) specification, which defines this syntax:
-
-```
-<type>: <summary>
-```
-
-The _type_ is the category of change that is made, possible types are:
-- `feat` - add a new feature or improve an existing feature
-- `fix` - fix a bug
-- `refactor` - refactor code without impact on features or performance
-- `docs` - add or edit code comments, documentation, GitHub pages
-- `style` - edit code style
-- `build` - retry failing build and anything build process related
-- `perf` - performance optimization
-- `ci` - continuous integration
-- `test` - tests
-
-The _summary_ is a short change description in present tense, not capitalized, without period at the end. This summary will also be used as the changelog entry.
-- It must be short and self-explanatory for a reader who does not see the details of the full pull request description
-- It must not contain abbreviations, e.g. instead of `LQ` write `LiveQuery`
-- It must use the correct product and feature names as referenced in the documentation, e.g. instead of `Cloud Validator` use `Cloud Function validation`
-- In case of a breaking change, the summary must not contain duplicate information that is also in the [BREAKING CHANGE](#breaking-change) chapter of the pull request description. It must not contain a note that it is a breaking change, as this will be automatically flagged as such if the pull request description contains the BREAKING CHANGE chapter.
-
-For example:
-
-```
-feat: add handle to door for easy opening
-```
-
-Currently, we are not making use of the commit _scope_, which would be written as `<type>(<scope>): <summary>`, that attributes a change to a specific part of the product.
-
-### Breaking Change
-
-If a pull request contains a braking change, the description of the pull request must contain a dedicated chapter at the bottom to indicate this. This is to assist the committer of the pull request to avoid merging a breaking change as non-breaking.
-
-## Merging
-
-The following guide is for anyone who merges a contributor pull request into the working branch, the working branch into a release branch, a release branch into another release branch, or any other direct commits such as hotfixes into release branches or the working branch.
-
-- A contributor pull request must be merged into the working branch using `Squash and Merge`, to create a single commit message that describes the change.
-- A release branch or the default branch must be merged into another release branch using `Merge Commit`, to preserve each individual commit message that describes its respective change.
-- For changelog generation, only the commit message set when merging the pull request is relevant. The title and description of the GitHub pull request as authored by the contributor have no influence on the changelog generation. However, the title of the GitHub pull request should be used as the commit message. See the following chapters for considerations in special scenarios, e.g. merging a breaking change or reverting a commit.
-
-### Breaking Change
-
-If the pull request contains a breaking change, the commit message must contain the phrase `BREAKING CHANGE`, capitalized and without any formatting, followed by a short description of the breaking change and ideally how the developer should address it, all in a single line. This line should contain more details focusing on the "breaking” aspect of the change and is intended to assist the developer in adapting. Keep it concise, as it will become part of the changelog entry, for example:
-
-  ```
-  fix: remove handle from door
-  
-  BREAKING CHANGE: You cannot open the door anymore by using a handle. See the [#migration guide](http://example.com) for more details.
-  ```
-  Keep in mind that in a repository with release automation, merging such a commit message will trigger a release with a major version increment.
-
-### Reverting
-
-If the commit reverts a previous commit, use the prefix `revert:`, followed by the header of the reverted commit. In the body of the commit message add `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted. For example:
-
-  ```
-  revert: fix: remove handle from door
-  
-  This reverts commit 1234567890abcdef.
-  ```
-
-⚠️ A `revert` prefix will *always* trigger a release. Generally, a commit that did not trigger a release when it was initially merged should also not trigger a release when it is reverted. For example, do not use the `revert` prefix when reverting a commit that has a `ci` prefix:
-
-  ```
-  ci: add something
-  ```
-  is reverted with:
-  ```
-  ci: remove something
-  ```
-  instead of:
-  ```
-  revert: ci: add something
-  
-  This reverts commit 1234567890abcdef.
-  ```
-
-### Security Vulnerability
-
-#### Local Testing
-
-Fixes for security vulnerabilities are developed in private forks with a closed audience, inaccessible to the public. A current GitHub limitation does not allow to run CI tests on pull requests in private forks. Whether a pull requests fully passes all CI tests can only be determined by publishing the fix as a public pull request and running the CI. This means the fix and implicitly information about the vulnerability are made accessible to the public. This increases the risk that a vulnerability fix is published, but then cannot be merged immediately due to a CI issue. To mitigate that risk, before publishing a vulnerability fix, the following tests needs to be run locally and pass:
-
-- `npm run test` to test with MongoDB
-- `npm run test:postgres:testonly` to test with Postgres
-- `npm run madge:circular` to detect circular dependencies
-- `npm run lint` to check lint compliance
-- `npm run definitions` to update the Parse Server options definitions
-
-> [!CAUTION]
-> It is essential to run `npm run build` *after* switching to a different branch or making a commit and *before*  running any tests. Otherwise the tests may run on the build from a different branch or on a build that does not reflect the most recent commits.
-
-#### Environment
-
-A reported vulnerability may have already been fixed since it was reported, either due to a targeted fix or as side-effect of other code changed. To verify that a vulnerability exists, tests need to be run in an environment that uses the latest commit of the development branch of Parse Server.
-
-> [!NOTE]
-> Do not use the latest alpha version for testing as it may be behind the latest commit of the development branch.
-
-Vulnerability test must only be conducted in environments for which the tester can ensure that no unauthorized 3rd party has potentially access to. This is to ensure a vulnerability stays confidential and is not exposed prematurely to the public.
-
-You must not test a vulnerability using any 3rd party APIs that provide Parse Server as a hosted service (SaaS) as this may expose the vulnerability to an unauthorized 3rd party and the effects of the vulnerability may cause issues on the provider's side. 
-
-> [!CAUTION]
-> Utilizing a vulnerability in a third-party service, even for testing or development purposes, can result in legal repercussions. You are solely accountable for any damage arising from such actions and agree to indemnify Parse Platform against any liabilities or claims resulting from your actions.
-
-#### Merging
-
-A current GitHub limitation does not allow to customize the commit message when merging pull requests of a private fork that was created to fix a security vulnerability. Our release automation framework demands a specific commit message syntax which therefore cannot be met. This prohibits to follow the process that GitHub suggest, which is to merge a pull request from a private fork directly to a public branch. Instead, after [local testing](#local-testing), a public pull request needs to be created with the code fix copied over from the private pull request.
-
-This creates a risk that a vulnerability is indirectly disclosed by publishing a pull request with the fix, but the fix cannot be merged due to a CI issue. To mitigate that risk, the pull request title and description should be kept marginal or generic, not hinting to a vulnerability or giving any details about the vulnerability, until the pull request has been successfully merged.
-
-## Releasing
-
-### General Considerations
-
-- The `package-lock.json` file has to be deleted and recreated by npm from scratch in regular intervals using the `npm i` command. It is not enough to only update the file via automated security pull requests (e.g. dependabot, snyk), that can create inconsistencies between sub-dependencies of a dependency and increase the chances of vulnerabilities. The file should be recreated once every release cycle which is usually monthly.
-
-### Major Release / Long-Term-Support
-
-While the current major version is published on branch `release`, a Long-Term-Support (LTS) version is published on branch `release-#.x.x`, for example `release-4.x.x` for the Parse Server 4.x LTS branch.
-
-### Preparing Release
-
-The following changes are done in the `alpha` branch, before publishing the last `beta` version that will eventually become the major release. This way the changes trickle naturally through all branches and code consistency is ensured among branches.
-
-- Make sure all [deprecations](https://github.com/parse-community/parse-server/blob/alpha/DEPRECATIONS.md) are reflected in code, old code is removed and the deprecations table is updated.
-- Add the future LTS branch `release-#.x.x` to the branch list in [release.config.js](https://github.com/parse-community/parse-server/blob/alpha/release.config.js) so that the branch will later be recognized for release automation.
-
-### Publishing Release (forward-merge):
-
-1. Create new temporary branch `build` on branch `beta`.
-2. Create PR to merge `build` into `release`:
-   - PR title: `build: release`
-   - PR description: (leave empty)
-3. Resolve any conflicts:
-   - For conflicts regarding the package version in `package.json` and `package-lock.json` it doesn't matter which version is chosen, as the version will be set by auto-release in a commit after merging. However, for both files the same version should be chosen when resolving the conflict.
-4. Merge PR with a "merge commit", do not "squash and merge":
-   - Commit message: (use PR title)
-   - Description: (leave empty)
-5. Wait for GitHub Action `release-automated` to finish:
-   - If GitHub Action fails, investigate why; manual correction may be needed.
-6. Pull all remote branches into local branches.
-7. Delete temporary branch `build`.
-8. Create new temporary branch `build` on branch `alpha`.
-9. Create PR to merge `build` into `beta`:
-   - PR title: `build: release`
-   - PR description: (leave empty)
-8. Repeat steps 3-7 for PR from step 9.
-
-### Publishing Hotfix (back-merge):
-
-1. Create PR to merge hotfix PR into `release`:
-   - Merge PR following the same rules as any PR would be merged into the working branch `alpha`.
-2. Wait for GitHub Action `release-automated` to finish:
-   - GitHub Action will fail with error `! [rejected] HEAD -> beta (non-fast-forward)`; this is expected as auto-release currently cannot fully handle back-merging; docker will not publish the new release, so this has to be done manually using the GitHub workflow `release-manual-docker` and entering the version tag that has been created by auto-release.
-3. Pull all remote branches into local branches.
-4. Create a new temporary branch `backmerge` on branch `release`.
-5. Create PR to merge `backmerge` into `beta`:
-   - PR title: `refactor: <commit-summary>` where `<commit-summary>` is the commit summary of step 1. The commit type needs to be `refactor`, otherwise the commit will show in the changelog of the `release` branch, once the `beta` branch is merged into release; this would a duplicate entry because the same changelog entry has already been generated when the PR was merged into the `release` branch in step 1.
-   - PR description: (leave empty)
-6. Resolve any conflicts:
-   - During back-merging, usually all changes are preserved; current changes come from the hotfix in the `release` branch, the incoming changes come from the `beta` branch usually being ahead of the `release` branch. This makes back-merging so complex and bug-prone and is the main reason why it should be avoided if possible.
-7. Merge PR with "squash and merge", do not do a "merge commit":
-   - Commit message: (use PR title)
-   - Description: (leave empty)
-  
-   ℹ️ Merging this PR will not trigger a release; the back-merge will not appear in changelogs of the `beta`, `alpha` branches; the back-merged fix will be an undocumented change of these branches' next releases; if necessary, the change needs to be added manually to the pre-release changelogs *after* the next pre-releases.
-8. Delete temporary branch `backmerge`.
-10. Create a new temporary branch `backmerge` on branch `beta`.
-11. Repeat steps 4-8 to merge PR into `alpha`.
-
-⚠️ Long-term-support branches are excluded from the processes above and handled individually as they do not have pre-releases branches and are not considered part of the current codebase anymore. It may be necessary to significantly adapt a PR for a LTS branch due to the differences in codebase and CI tests. This adaption should be done in advance before merging any related PR, especially for security fixes, as to not publish a vulnerability while it may still take significant time to adapt the fix for the older codebase of a LTS branch.
-
-### Publishing Major Release (Yearly Release)
-
-1. Create LTS branch `release-#.x.x` off the latest version tag on `release` branch.
-2. Create temporary branch `build-release` off branch `beta` and create a pull request with `release` as the base branch.
-3. Merge branch `build-release` into `release`. Given that there will be breaking changes, a new major release will be created. In the unlikely case that there have been no breaking changes between the previous major release and the upcoming release, a major version increment has to be triggered manually. See the docs of the release automation framework for how to do that.
-4. Add newly created LTS branch `release-#.x.x` from step 1 to [Snyk](https://snyk.io) so that Snyk opens pull requests for the LTS branch; remove previously existing LTS branch `release-#.x.x` from Snyk.
-
-## Versioning
-
-> The following versioning system is applied since Parse Server 5.0.0 and does not necessarily apply to previous releases.
-
-Parse Server follows [semantic versioning](https://semver.org) with a flavor of [calendric versioning](https://calver.org). Semantic versioning makes Parse Server easy to upgrade because breaking changes only occur in major releases. Calendric versioning gives an additional sense of how old a Parse Server release is and allows for Long-Term Support of previous major releases.
-
-Example version: `5.0.0-alpha.1`
-
-Syntax: `[major]`**.**`[minor]`**.**`[patch]`**-**`[pre-release-label]`**.**`[pre-release-increment]`
-
-- The `major` version increments with the first release of every year and may include changes that are *not backwards compatible*.
-- The `minor` version increments during the year and may include new features or improvements of existing features that are backwards compatible.
-- The `patch` version increments during the year and may include bug fixes that are backwards compatible.
-- The `pre-release-label` is optional for pre-release versions such as:
-  - `-alpha` (likely to contain bugs, likely to change in features until release)
-  - `-beta` (likely to contain bugs, no change in features until release)
-- The `[pre-release-increment]` is a number that increments with every new version of a pre-release
-
-Exceptions:
-- The `major` version may increment during the year in the unlikely event that a breaking change is so urgent that it cannot wait for the next yearly release. An example would be a vulnerability fix that leads to an unavoidable breaking change. However, security requirements depend on the application and not every vulnerability may affect every deployment, depending on the features used. Therefore we usually prefer to deprecate insecure functionality and introduce the breaking change following our [deprecation policy](#deprecation-policy).
-
-## Code of Conduct
-
-This project adheres to the [Contributor Covenant Code of Conduct](https://github.com/parse-community/parse-server/blob/master/CODE_OF_CONDUCT.md). By participating, you are expected to honor this code.
-
-[config]: http://parseplatform.org/parse-server/api/master/ParseServerOptions.html
-[config-def]: https://github.com/parse-community/parse-server/blob/master/src/Options/Definitions.js
-[config-docs]: https://github.com/parse-community/parse-server/blob/master/src/Options/docs.js
-[config-index]: https://github.com/parse-community/parse-server/blob/master/src/Options/index.js

DEPRECATIONS.md

@@ -1,22 +0,0 @@
-# Deprecation Plan <!-- omit in toc -->
-
-The following is a list of deprecations, according to the [Deprecation Policy](https://github.com/parse-community/parse-server/blob/master/CONTRIBUTING.md#deprecation-policy). After a feature becomes deprecated, and giving developers time to adapt to the change, the deprecated feature will eventually be removed, leading to a breaking change. Developer feedback during the deprecation period may postpone or even revoke the introduction of the breaking change.
-
-| ID      | Change                                                                                       | Issue                                                                | Deprecation [ℹ️][i_deprecation] | Planned Removal [ℹ️][i_removal] | Status [ℹ️][i_status] | Notes |
-|---------|----------------------------------------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------|---------------------------------|-----------------------|-------|
-| DEPPS1  | Native MongoDB syntax in aggregation pipeline                                                | [#7338](https://github.com/parse-community/parse-server/issues/7338) | 5.0.0 (2022)                    | 6.0.0 (2023)                    | removed               | -     |
-| DEPPS2  | Config option `directAccess` defaults to `true`                                              | [#6636](https://github.com/parse-community/parse-server/pull/6636)   | 5.0.0 (2022)                    | 6.0.0 (2023)                    | removed               | -     |
-| DEPPS3  | Config option `enforcePrivateUsers` defaults to `true`                                       | [#7319](https://github.com/parse-community/parse-server/pull/7319)   | 5.0.0 (2022)                    | 6.0.0 (2023)                    | removed               | -     |
-| DEPPS4  | Remove convenience method for http request `Parse.Cloud.httpRequest`                         | [#7589](https://github.com/parse-community/parse-server/pull/7589)   | 5.0.0 (2022)                    | 6.0.0 (2023)                    | removed               | -     |
-| DEPPS5  | Config option `allowClientClassCreation` defaults to `false`                                 | [#7925](https://github.com/parse-community/parse-server/pull/7925)   | 5.3.0 (2022)                    | 7.0.0 (2024)                    | removed               | -     |
-| DEPPS6  | Auth providers disabled by default                                                           | [#7953](https://github.com/parse-community/parse-server/pull/7953)   | 5.3.0 (2022)                    | 7.0.0 (2024)                    | removed               | -     |
-| DEPPS7  | Remove file trigger syntax `Parse.Cloud.beforeSaveFile((request) => {})`                     | [#7966](https://github.com/parse-community/parse-server/pull/7966)   | 5.3.0 (2022)                    | 7.0.0 (2024)                    | removed               | -     |
-| DEPPS8  | Login with expired 3rd party authentication token defaults to `false`                        | [#7079](https://github.com/parse-community/parse-server/pull/7079)   | 5.3.0 (2022)                    | 7.0.0 (2024)                    | removed               | -     |
-| DEPPS9  | Rename LiveQuery `fields` option to `keys`                                                   | [#8389](https://github.com/parse-community/parse-server/issues/8389) | 6.0.0 (2023)                    | 7.0.0 (2024)                    | removed               | -     |
-| DEPPS10 | Encode `Parse.Object` in Cloud Function and remove option `encodeParseObjectInCloudFunction` | [#8634](https://github.com/parse-community/parse-server/issues/8634) | 6.2.0 (2023)                    | 9.0.0 (2026)                    | deprecated            | -     |
-| DEPPS11 | Replace `PublicAPIRouter` with `PagesRouter`                                                 | [#7625](https://github.com/parse-community/parse-server/issues/7625) | 8.0.0 (2025)                    | 9.0.0 (2026)                    | deprecated            | -     |
-| DEPPS12 | Database option `allowPublicExplain` will default to `true`                                  | [#7519](https://github.com/parse-community/parse-server/issues/7519) | 8.5.0 (2025)                    | 9.0.0 (2026)                    | deprecated            | -     |
-
-[i_deprecation]: ## "The version and date of the deprecation."
-[i_removal]: ## "The version and date of the planned removal."
-[i_status]: ## "The current status of the deprecation: deprecated (the feature is deprecated and still available), removed (the deprecated feature has been removed and is unavailable), retracted (the deprecation has been retracted and the feature will not be removed."

Dockerfile

@@ -1,51 +0,0 @@
-############################################################
-# Build stage
-############################################################
-FROM node:20.19.0-alpine3.20 AS build
-
-RUN apk --no-cache add \
-   build-base \
-   git \
-   python3
-
-WORKDIR /tmp
-
-# Copy package.json first to benefit from layer caching
-COPY package*.json ./
-
-# Copy src to have config files for install
-COPY . .
-
-# Install without scripts
-RUN npm ci --omit=dev --ignore-scripts \
-    # Copy production node_modules aside for later
- && cp -R node_modules prod_node_modules \
-    # Install all dependencies
- && npm ci \
-    # Run build steps
- && npm run build
-
-############################################################
-# Release stage
-############################################################
-FROM node:20.19.0-alpine3.20 AS release
-
-VOLUME /parse-server/cloud /parse-server/config
-
-WORKDIR /parse-server
-
-# Copy build stage folders
-COPY --from=build /tmp/prod_node_modules /parse-server/node_modules
-COPY --from=build /tmp/lib lib
-
-COPY package*.json ./
-COPY bin bin
-COPY public_html public_html
-COPY views views
-RUN mkdir -p logs && chown -R node: logs
-
-ENV PORT=1337
-USER node
-EXPOSE $PORT
-
-ENTRYPOINT ["node", "./bin/parse-server"]

LICENSE

@@ -1,176 +0,0 @@
-                      Apache License
-                  Version 2.0, January 2004
-               http://www.apache.org/licenses/
-
-TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-1. Definitions.
-
-  "License" shall mean the terms and conditions for use, reproduction,
-  and distribution as defined by Sections 1 through 9 of this document.
-
-  "Licensor" shall mean the copyright owner or entity authorized by
-  the copyright owner that is granting the License.
-
-  "Legal Entity" shall mean the union of the acting entity and all
-  other entities that control, are controlled by, or are under common
-  control with that entity. For the purposes of this definition,
-  "control" means (i) the power, direct or indirect, to cause the
-  direction or management of such entity, whether by contract or
-  otherwise, or (ii) ownership of fifty percent (50%) or more of the
-  outstanding shares, or (iii) beneficial ownership of such entity.
-
-  "You" (or "Your") shall mean an individual or Legal Entity
-  exercising permissions granted by this License.
-
-  "Source" form shall mean the preferred form for making modifications,
-  including but not limited to software source code, documentation
-  source, and configuration files.
-
-  "Object" form shall mean any form resulting from mechanical
-  transformation or translation of a Source form, including but
-  not limited to compiled object code, generated documentation,
-  and conversions to other media types.
-
-  "Work" shall mean the work of authorship, whether in Source or
-  Object form, made available under the License, as indicated by a
-  copyright notice that is included in or attached to the work
-  (an example is provided in the Appendix below).
-
-  "Derivative Works" shall mean any work, whether in Source or Object
-  form, that is based on (or derived from) the Work and for which the
-  editorial revisions, annotations, elaborations, or other modifications
-  represent, as a whole, an original work of authorship. For the purposes
-  of this License, Derivative Works shall not include works that remain
-  separable from, or merely link (or bind by name) to the interfaces of,
-  the Work and Derivative Works thereof.
-
-  "Contribution" shall mean any work of authorship, including
-  the original version of the Work and any modifications or additions
-  to that Work or Derivative Works thereof, that is intentionally
-  submitted to Licensor for inclusion in the Work by the copyright owner
-  or by an individual or Legal Entity authorized to submit on behalf of
-  the copyright owner. For the purposes of this definition, "submitted"
-  means any form of electronic, verbal, or written communication sent
-  to the Licensor or its representatives, including but not limited to
-  communication on electronic mailing lists, source code control systems,
-  and issue tracking systems that are managed by, or on behalf of, the
-  Licensor for the purpose of discussing and improving the Work, but
-  excluding communication that is conspicuously marked or otherwise
-  designated in writing by the copyright owner as "Not a Contribution."
-
-  "Contributor" shall mean Licensor and any individual or Legal Entity
-  on behalf of whom a Contribution has been received by Licensor and
-  subsequently incorporated within the Work.
-
-2. Grant of Copyright License. Subject to the terms and conditions of
-  this License, each Contributor hereby grants to You a perpetual,
-  worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-  copyright license to reproduce, prepare Derivative Works of,
-  publicly display, publicly perform, sublicense, and distribute the
-  Work and such Derivative Works in Source or Object form.
-
-3. Grant of Patent License. Subject to the terms and conditions of
-  this License, each Contributor hereby grants to You a perpetual,
-  worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-  (except as stated in this section) patent license to make, have made,
-  use, offer to sell, sell, import, and otherwise transfer the Work,
-  where such license applies only to those patent claims licensable
-  by such Contributor that are necessarily infringed by their
-  Contribution(s) alone or by combination of their Contribution(s)
-  with the Work to which such Contribution(s) was submitted. If You
-  institute patent litigation against any entity (including a
-  cross-claim or counterclaim in a lawsuit) alleging that the Work
-  or a Contribution incorporated within the Work constitutes direct
-  or contributory patent infringement, then any patent licenses
-  granted to You under this License for that Work shall terminate
-  as of the date such litigation is filed.
-
-4. Redistribution. You may reproduce and distribute copies of the
-  Work or Derivative Works thereof in any medium, with or without
-  modifications, and in Source or Object form, provided that You
-  meet the following conditions:
-
-  (a) You must give any other recipients of the Work or
-      Derivative Works a copy of this License; and
-
-  (b) You must cause any modified files to carry prominent notices
-      stating that You changed the files; and
-
-  (c) You must retain, in the Source form of any Derivative Works
-      that You distribute, all copyright, patent, trademark, and
-      attribution notices from the Source form of the Work,
-      excluding those notices that do not pertain to any part of
-      the Derivative Works; and
-
-  (d) If the Work includes a "NOTICE" text file as part of its
-      distribution, then any Derivative Works that You distribute must
-      include a readable copy of the attribution notices contained
-      within such NOTICE file, excluding those notices that do not
-      pertain to any part of the Derivative Works, in at least one
-      of the following places: within a NOTICE text file distributed
-      as part of the Derivative Works; within the Source form or
-      documentation, if provided along with the Derivative Works; or,
-      within a display generated by the Derivative Works, if and
-      wherever such third-party notices normally appear. The contents
-      of the NOTICE file are for informational purposes only and
-      do not modify the License. You may add Your own attribution
-      notices within Derivative Works that You distribute, alongside
-      or as an addendum to the NOTICE text from the Work, provided
-      that such additional attribution notices cannot be construed
-      as modifying the License.
-
-  You may add Your own copyright statement to Your modifications and
-  may provide additional or different license terms and conditions
-  for use, reproduction, or distribution of Your modifications, or
-  for any such Derivative Works as a whole, provided Your use,
-  reproduction, and distribution of the Work otherwise complies with
-  the conditions stated in this License.
-
-5. Submission of Contributions. Unless You explicitly state otherwise,
-  any Contribution intentionally submitted for inclusion in the Work
-  by You to the Licensor shall be under the terms and conditions of
-  this License, without any additional terms or conditions.
-  Notwithstanding the above, nothing herein shall supersede or modify
-  the terms of any separate license agreement you may have executed
-  with Licensor regarding such Contributions.
-
-6. Trademarks. This License does not grant permission to use the trade
-  names, trademarks, service marks, or product names of the Licensor,
-  except as required for reasonable and customary use in describing the
-  origin of the Work and reproducing the content of the NOTICE file.
-
-7. Disclaimer of Warranty. Unless required by applicable law or
-  agreed to in writing, Licensor provides the Work (and each
-  Contributor provides its Contributions) on an "AS IS" BASIS,
-  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-  implied, including, without limitation, any warranties or conditions
-  of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-  PARTICULAR PURPOSE. You are solely responsible for determining the
-  appropriateness of using or redistributing the Work and assume any
-  risks associated with Your exercise of permissions under this License.
-
-8. Limitation of Liability. In no event and under no legal theory,
-  whether in tort (including negligence), contract, or otherwise,
-  unless required by applicable law (such as deliberate and grossly
-  negligent acts) or agreed to in writing, shall any Contributor be
-  liable to You for damages, including any direct, indirect, special,
-  incidental, or consequential damages of any character arising as a
-  result of this License or out of the use or inability to use the
-  Work (including but not limited to damages for loss of goodwill,
-  work stoppage, computer failure or malfunction, or any and all
-  other commercial damages or losses), even if such Contributor
-  has been advised of the possibility of such damages.
-
-9. Accepting Warranty or Additional Liability. While redistributing
-  the Work or Derivative Works thereof, You may choose to offer,
-  and charge a fee for, acceptance of support, warranty, indemnity,
-  or other liability obligations and/or rights consistent with this
-  License. However, in accepting such obligations, You may act only
-  on Your own behalf and on Your sole responsibility, not on behalf
-  of any other Contributor, and only if You agree to indemnify,
-  defend, and hold each Contributor harmless for any liability
-  incurred by, or claims asserted against, such Contributor by reason
-  of your accepting any such warranty or additional liability.
-
-END OF TERMS AND CONDITIONS

NOTICE

@@ -1,10 +0,0 @@
-Parse Server
-
-Copyright 2015-present Parse Platform
-
-This product includes software developed at Parse Platform.
-www.parseplatform.org
-
----
-
-As of April 5, 2017, Parse, LLC has transferred this code to the Parse Platform organization, and will no longer be contributing to or distributing this code.

SECURITY.md

@@ -1,19 +0,0 @@
-# Parse Community Vulnerability Disclosure Program
-If you believe you have found a security vulnerability on one of parse-community maintained packages,
-we encourage you to let us know right away. 
-We will investigate all legitimate reports and do our best to quickly fix the problem. 
-Before making a report, please review this page to understand our disclosure policy and how to communicate with us.
-
-# Responsible Disclosure Policy
-If you comply with the policies below when reporting a security issue to parse community, 
-we will not initiate a lawsuit or law enforcement investigation against you in response to your report.
-We ask that: 
-
-- You give us reasonable time to investigate and mitigate an issue you report before making public any information about the report or sharing such information with others. This means we request _at least_ **7 days** to get back to you with an initial response and _at least_ **30 days** from initial contact (made by you) to apply a patch.
-- You do not interact with an individual account (which includes modifying or accessing data from the account) if the account owner has not consented to such actions.
-- You make a good faith effort to avoid privacy violations and disruptions to others, including (but not limited to) destruction of data and interruption or degradation of our services.
-- You do not exploit a security issue you discover for any reason. (This includes demonstrating additional risk, such as attempted compromise of sensitive company data or probing for additional issues). You do not violate any other applicable laws or regulations.
-
-# Communicating with us
-
-All vulnerabilities should be privately reported to us by going to [https://report.parseplatform.org](https://report.parseplatform.org). Alternatively, you can send an email to [security@parseplatform.org](mailto:security@parseplatform.org).

api/''/scripts/linenumber.js

@@ -0,0 +1,25 @@
+/*global document */
+(function() {
+    var source = document.getElementsByClassName('prettyprint source linenums');
+    var i = 0;
+    var lineNumber = 0;
+    var lineId;
+    var lines;
+    var totalLines;
+    var anchorHash;
+
+    if (source && source[0]) {
+        anchorHash = document.location.hash.substring(1);
+        lines = source[0].getElementsByTagName('li');
+        totalLines = lines.length;
+
+        for (; i < totalLines; i++) {
+            lineNumber++;
+            lineId = 'line' + lineNumber;
+            lines[i].id = lineId;
+            if (lineId === anchorHash) {
+                lines[i].className += ' selected';
+            }
+        }
+    }
+})();

api/''/scripts/prettify/Apache-License-2.0.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

api/''/scripts/prettify/lang-css.js

@@ -0,0 +1,2 @@
+PR.registerLangHandler(PR.createSimpleLexer([["pln",/^[\t\n\f\r ]+/,null," \t\r\n"]],[["str",/^"(?:[^\n\f\r"\\]|\\(?:\r\n?|\n|\f)|\\[\S\s])*"/,null],["str",/^'(?:[^\n\f\r'\\]|\\(?:\r\n?|\n|\f)|\\[\S\s])*'/,null],["lang-css-str",/^url\(([^"')]*)\)/i],["kwd",/^(?:url|rgb|!important|@import|@page|@media|@charset|inherit)(?=[^\w-]|$)/i,null],["lang-css-kw",/^(-?(?:[_a-z]|\\[\da-f]+ ?)(?:[\w-]|\\\\[\da-f]+ ?)*)\s*:/i],["com",/^\/\*[^*]*\*+(?:[^*/][^*]*\*+)*\//],["com",
+/^(?:<\!--|--\>)/],["lit",/^(?:\d+|\d*\.\d+)(?:%|[a-z]+)?/i],["lit",/^#[\da-f]{3,6}/i],["pln",/^-?(?:[_a-z]|\\[\da-f]+ ?)(?:[\w-]|\\\\[\da-f]+ ?)*/i],["pun",/^[^\s\w"']+/]]),["css"]);PR.registerLangHandler(PR.createSimpleLexer([],[["kwd",/^-?(?:[_a-z]|\\[\da-f]+ ?)(?:[\w-]|\\\\[\da-f]+ ?)*/i]]),["css-kw"]);PR.registerLangHandler(PR.createSimpleLexer([],[["str",/^[^"')]+/]]),["css-str"]);

api/''/scripts/prettify/prettify.js

@@ -0,0 +1,28 @@
+var q=null;window.PR_SHOULD_USE_CONTINUATION=!0;
+(function(){function L(a){function m(a){var f=a.charCodeAt(0);if(f!==92)return f;var b=a.charAt(1);return(f=r[b])?f:"0"<=b&&b<="7"?parseInt(a.substring(1),8):b==="u"||b==="x"?parseInt(a.substring(2),16):a.charCodeAt(1)}function e(a){if(a<32)return(a<16?"\\x0":"\\x")+a.toString(16);a=String.fromCharCode(a);if(a==="\\"||a==="-"||a==="["||a==="]")a="\\"+a;return a}function h(a){for(var f=a.substring(1,a.length-1).match(/\\u[\dA-Fa-f]{4}|\\x[\dA-Fa-f]{2}|\\[0-3][0-7]{0,2}|\\[0-7]{1,2}|\\[\S\s]|[^\\]/g),a=
+[],b=[],o=f[0]==="^",c=o?1:0,i=f.length;c<i;++c){var j=f[c];if(/\\[bdsw]/i.test(j))a.push(j);else{var j=m(j),d;c+2<i&&"-"===f[c+1]?(d=m(f[c+2]),c+=2):d=j;b.push([j,d]);d<65||j>122||(d<65||j>90||b.push([Math.max(65,j)|32,Math.min(d,90)|32]),d<97||j>122||b.push([Math.max(97,j)&-33,Math.min(d,122)&-33]))}}b.sort(function(a,f){return a[0]-f[0]||f[1]-a[1]});f=[];j=[NaN,NaN];for(c=0;c<b.length;++c)i=b[c],i[0]<=j[1]+1?j[1]=Math.max(j[1],i[1]):f.push(j=i);b=["["];o&&b.push("^");b.push.apply(b,a);for(c=0;c<
+f.length;++c)i=f[c],b.push(e(i[0])),i[1]>i[0]&&(i[1]+1>i[0]&&b.push("-"),b.push(e(i[1])));b.push("]");return b.join("")}function y(a){for(var f=a.source.match(/\[(?:[^\\\]]|\\[\S\s])*]|\\u[\dA-Fa-f]{4}|\\x[\dA-Fa-f]{2}|\\\d+|\\[^\dux]|\(\?[!:=]|[()^]|[^()[\\^]+/g),b=f.length,d=[],c=0,i=0;c<b;++c){var j=f[c];j==="("?++i:"\\"===j.charAt(0)&&(j=+j.substring(1))&&j<=i&&(d[j]=-1)}for(c=1;c<d.length;++c)-1===d[c]&&(d[c]=++t);for(i=c=0;c<b;++c)j=f[c],j==="("?(++i,d[i]===void 0&&(f[c]="(?:")):"\\"===j.charAt(0)&&
+(j=+j.substring(1))&&j<=i&&(f[c]="\\"+d[i]);for(i=c=0;c<b;++c)"^"===f[c]&&"^"!==f[c+1]&&(f[c]="");if(a.ignoreCase&&s)for(c=0;c<b;++c)j=f[c],a=j.charAt(0),j.length>=2&&a==="["?f[c]=h(j):a!=="\\"&&(f[c]=j.replace(/[A-Za-z]/g,function(a){a=a.charCodeAt(0);return"["+String.fromCharCode(a&-33,a|32)+"]"}));return f.join("")}for(var t=0,s=!1,l=!1,p=0,d=a.length;p<d;++p){var g=a[p];if(g.ignoreCase)l=!0;else if(/[a-z]/i.test(g.source.replace(/\\u[\da-f]{4}|\\x[\da-f]{2}|\\[^UXux]/gi,""))){s=!0;l=!1;break}}for(var r=
+{b:8,t:9,n:10,v:11,f:12,r:13},n=[],p=0,d=a.length;p<d;++p){g=a[p];if(g.global||g.multiline)throw Error(""+g);n.push("(?:"+y(g)+")")}return RegExp(n.join("|"),l?"gi":"g")}function M(a){function m(a){switch(a.nodeType){case 1:if(e.test(a.className))break;for(var g=a.firstChild;g;g=g.nextSibling)m(g);g=a.nodeName;if("BR"===g||"LI"===g)h[s]="\n",t[s<<1]=y++,t[s++<<1|1]=a;break;case 3:case 4:g=a.nodeValue,g.length&&(g=p?g.replace(/\r\n?/g,"\n"):g.replace(/[\t\n\r ]+/g," "),h[s]=g,t[s<<1]=y,y+=g.length,
+t[s++<<1|1]=a)}}var e=/(?:^|\s)nocode(?:\s|$)/,h=[],y=0,t=[],s=0,l;a.currentStyle?l=a.currentStyle.whiteSpace:window.getComputedStyle&&(l=document.defaultView.getComputedStyle(a,q).getPropertyValue("white-space"));var p=l&&"pre"===l.substring(0,3);m(a);return{a:h.join("").replace(/\n$/,""),c:t}}function B(a,m,e,h){m&&(a={a:m,d:a},e(a),h.push.apply(h,a.e))}function x(a,m){function e(a){for(var l=a.d,p=[l,"pln"],d=0,g=a.a.match(y)||[],r={},n=0,z=g.length;n<z;++n){var f=g[n],b=r[f],o=void 0,c;if(typeof b===
+"string")c=!1;else{var i=h[f.charAt(0)];if(i)o=f.match(i[1]),b=i[0];else{for(c=0;c<t;++c)if(i=m[c],o=f.match(i[1])){b=i[0];break}o||(b="pln")}if((c=b.length>=5&&"lang-"===b.substring(0,5))&&!(o&&typeof o[1]==="string"))c=!1,b="src";c||(r[f]=b)}i=d;d+=f.length;if(c){c=o[1];var j=f.indexOf(c),k=j+c.length;o[2]&&(k=f.length-o[2].length,j=k-c.length);b=b.substring(5);B(l+i,f.substring(0,j),e,p);B(l+i+j,c,C(b,c),p);B(l+i+k,f.substring(k),e,p)}else p.push(l+i,b)}a.e=p}var h={},y;(function(){for(var e=a.concat(m),
+l=[],p={},d=0,g=e.length;d<g;++d){var r=e[d],n=r[3];if(n)for(var k=n.length;--k>=0;)h[n.charAt(k)]=r;r=r[1];n=""+r;p.hasOwnProperty(n)||(l.push(r),p[n]=q)}l.push(/[\S\s]/);y=L(l)})();var t=m.length;return e}function u(a){var m=[],e=[];a.tripleQuotedStrings?m.push(["str",/^(?:'''(?:[^'\\]|\\[\S\s]|''?(?=[^']))*(?:'''|$)|"""(?:[^"\\]|\\[\S\s]|""?(?=[^"]))*(?:"""|$)|'(?:[^'\\]|\\[\S\s])*(?:'|$)|"(?:[^"\\]|\\[\S\s])*(?:"|$))/,q,"'\""]):a.multiLineStrings?m.push(["str",/^(?:'(?:[^'\\]|\\[\S\s])*(?:'|$)|"(?:[^"\\]|\\[\S\s])*(?:"|$)|`(?:[^\\`]|\\[\S\s])*(?:`|$))/,
+q,"'\"`"]):m.push(["str",/^(?:'(?:[^\n\r'\\]|\\.)*(?:'|$)|"(?:[^\n\r"\\]|\\.)*(?:"|$))/,q,"\"'"]);a.verbatimStrings&&e.push(["str",/^@"(?:[^"]|"")*(?:"|$)/,q]);var h=a.hashComments;h&&(a.cStyleComments?(h>1?m.push(["com",/^#(?:##(?:[^#]|#(?!##))*(?:###|$)|.*)/,q,"#"]):m.push(["com",/^#(?:(?:define|elif|else|endif|error|ifdef|include|ifndef|line|pragma|undef|warning)\b|[^\n\r]*)/,q,"#"]),e.push(["str",/^<(?:(?:(?:\.\.\/)*|\/?)(?:[\w-]+(?:\/[\w-]+)+)?[\w-]+\.h|[a-z]\w*)>/,q])):m.push(["com",/^#[^\n\r]*/,
+q,"#"]));a.cStyleComments&&(e.push(["com",/^\/\/[^\n\r]*/,q]),e.push(["com",/^\/\*[\S\s]*?(?:\*\/|$)/,q]));a.regexLiterals&&e.push(["lang-regex",/^(?:^^\.?|[!+-]|!=|!==|#|%|%=|&|&&|&&=|&=|\(|\*|\*=|\+=|,|-=|->|\/|\/=|:|::|;|<|<<|<<=|<=|=|==|===|>|>=|>>|>>=|>>>|>>>=|[?@[^]|\^=|\^\^|\^\^=|{|\||\|=|\|\||\|\|=|~|break|case|continue|delete|do|else|finally|instanceof|return|throw|try|typeof)\s*(\/(?=[^*/])(?:[^/[\\]|\\[\S\s]|\[(?:[^\\\]]|\\[\S\s])*(?:]|$))+\/)/]);(h=a.types)&&e.push(["typ",h]);a=(""+a.keywords).replace(/^ | $/g,
+"");a.length&&e.push(["kwd",RegExp("^(?:"+a.replace(/[\s,]+/g,"|")+")\\b"),q]);m.push(["pln",/^\s+/,q," \r\n\t\xa0"]);e.push(["lit",/^@[$_a-z][\w$@]*/i,q],["typ",/^(?:[@_]?[A-Z]+[a-z][\w$@]*|\w+_t\b)/,q],["pln",/^[$_a-z][\w$@]*/i,q],["lit",/^(?:0x[\da-f]+|(?:\d(?:_\d+)*\d*(?:\.\d*)?|\.\d\+)(?:e[+-]?\d+)?)[a-z]*/i,q,"0123456789"],["pln",/^\\[\S\s]?/,q],["pun",/^.[^\s\w"-$'./@\\`]*/,q]);return x(m,e)}function D(a,m){function e(a){switch(a.nodeType){case 1:if(k.test(a.className))break;if("BR"===a.nodeName)h(a),
+a.parentNode&&a.parentNode.removeChild(a);else for(a=a.firstChild;a;a=a.nextSibling)e(a);break;case 3:case 4:if(p){var b=a.nodeValue,d=b.match(t);if(d){var c=b.substring(0,d.index);a.nodeValue=c;(b=b.substring(d.index+d[0].length))&&a.parentNode.insertBefore(s.createTextNode(b),a.nextSibling);h(a);c||a.parentNode.removeChild(a)}}}}function h(a){function b(a,d){var e=d?a.cloneNode(!1):a,f=a.parentNode;if(f){var f=b(f,1),g=a.nextSibling;f.appendChild(e);for(var h=g;h;h=g)g=h.nextSibling,f.appendChild(h)}return e}
+for(;!a.nextSibling;)if(a=a.parentNode,!a)return;for(var a=b(a.nextSibling,0),e;(e=a.parentNode)&&e.nodeType===1;)a=e;d.push(a)}var k=/(?:^|\s)nocode(?:\s|$)/,t=/\r\n?|\n/,s=a.ownerDocument,l;a.currentStyle?l=a.currentStyle.whiteSpace:window.getComputedStyle&&(l=s.defaultView.getComputedStyle(a,q).getPropertyValue("white-space"));var p=l&&"pre"===l.substring(0,3);for(l=s.createElement("LI");a.firstChild;)l.appendChild(a.firstChild);for(var d=[l],g=0;g<d.length;++g)e(d[g]);m===(m|0)&&d[0].setAttribute("value",
+m);var r=s.createElement("OL");r.className="linenums";for(var n=Math.max(0,m-1|0)||0,g=0,z=d.length;g<z;++g)l=d[g],l.className="L"+(g+n)%10,l.firstChild||l.appendChild(s.createTextNode("\xa0")),r.appendChild(l);a.appendChild(r)}function k(a,m){for(var e=m.length;--e>=0;){var h=m[e];A.hasOwnProperty(h)?window.console&&console.warn("cannot override language handler %s",h):A[h]=a}}function C(a,m){if(!a||!A.hasOwnProperty(a))a=/^\s*</.test(m)?"default-markup":"default-code";return A[a]}function E(a){var m=
+a.g;try{var e=M(a.h),h=e.a;a.a=h;a.c=e.c;a.d=0;C(m,h)(a);var k=/\bMSIE\b/.test(navigator.userAgent),m=/\n/g,t=a.a,s=t.length,e=0,l=a.c,p=l.length,h=0,d=a.e,g=d.length,a=0;d[g]=s;var r,n;for(n=r=0;n<g;)d[n]!==d[n+2]?(d[r++]=d[n++],d[r++]=d[n++]):n+=2;g=r;for(n=r=0;n<g;){for(var z=d[n],f=d[n+1],b=n+2;b+2<=g&&d[b+1]===f;)b+=2;d[r++]=z;d[r++]=f;n=b}for(d.length=r;h<p;){var o=l[h+2]||s,c=d[a+2]||s,b=Math.min(o,c),i=l[h+1],j;if(i.nodeType!==1&&(j=t.substring(e,b))){k&&(j=j.replace(m,"\r"));i.nodeValue=
+j;var u=i.ownerDocument,v=u.createElement("SPAN");v.className=d[a+1];var x=i.parentNode;x.replaceChild(v,i);v.appendChild(i);e<o&&(l[h+1]=i=u.createTextNode(t.substring(b,o)),x.insertBefore(i,v.nextSibling))}e=b;e>=o&&(h+=2);e>=c&&(a+=2)}}catch(w){"console"in window&&console.log(w&&w.stack?w.stack:w)}}var v=["break,continue,do,else,for,if,return,while"],w=[[v,"auto,case,char,const,default,double,enum,extern,float,goto,int,long,register,short,signed,sizeof,static,struct,switch,typedef,union,unsigned,void,volatile"],
+"catch,class,delete,false,import,new,operator,private,protected,public,this,throw,true,try,typeof"],F=[w,"alignof,align_union,asm,axiom,bool,concept,concept_map,const_cast,constexpr,decltype,dynamic_cast,explicit,export,friend,inline,late_check,mutable,namespace,nullptr,reinterpret_cast,static_assert,static_cast,template,typeid,typename,using,virtual,where"],G=[w,"abstract,boolean,byte,extends,final,finally,implements,import,instanceof,null,native,package,strictfp,super,synchronized,throws,transient"],
+H=[G,"as,base,by,checked,decimal,delegate,descending,dynamic,event,fixed,foreach,from,group,implicit,in,interface,internal,into,is,lock,object,out,override,orderby,params,partial,readonly,ref,sbyte,sealed,stackalloc,string,select,uint,ulong,unchecked,unsafe,ushort,var"],w=[w,"debugger,eval,export,function,get,null,set,undefined,var,with,Infinity,NaN"],I=[v,"and,as,assert,class,def,del,elif,except,exec,finally,from,global,import,in,is,lambda,nonlocal,not,or,pass,print,raise,try,with,yield,False,True,None"],
+J=[v,"alias,and,begin,case,class,def,defined,elsif,end,ensure,false,in,module,next,nil,not,or,redo,rescue,retry,self,super,then,true,undef,unless,until,when,yield,BEGIN,END"],v=[v,"case,done,elif,esac,eval,fi,function,in,local,set,then,until"],K=/^(DIR|FILE|vector|(de|priority_)?queue|list|stack|(const_)?iterator|(multi)?(set|map)|bitset|u?(int|float)\d*)/,N=/\S/,O=u({keywords:[F,H,w,"caller,delete,die,do,dump,elsif,eval,exit,foreach,for,goto,if,import,last,local,my,next,no,our,print,package,redo,require,sub,undef,unless,until,use,wantarray,while,BEGIN,END"+
+I,J,v],hashComments:!0,cStyleComments:!0,multiLineStrings:!0,regexLiterals:!0}),A={};k(O,["default-code"]);k(x([],[["pln",/^[^<?]+/],["dec",/^<!\w[^>]*(?:>|$)/],["com",/^<\!--[\S\s]*?(?:--\>|$)/],["lang-",/^<\?([\S\s]+?)(?:\?>|$)/],["lang-",/^<%([\S\s]+?)(?:%>|$)/],["pun",/^(?:<[%?]|[%?]>)/],["lang-",/^<xmp\b[^>]*>([\S\s]+?)<\/xmp\b[^>]*>/i],["lang-js",/^<script\b[^>]*>([\S\s]*?)(<\/script\b[^>]*>)/i],["lang-css",/^<style\b[^>]*>([\S\s]*?)(<\/style\b[^>]*>)/i],["lang-in.tag",/^(<\/?[a-z][^<>]*>)/i]]),
+["default-markup","htm","html","mxml","xhtml","xml","xsl"]);k(x([["pln",/^\s+/,q," \t\r\n"],["atv",/^(?:"[^"]*"?|'[^']*'?)/,q,"\"'"]],[["tag",/^^<\/?[a-z](?:[\w-.:]*\w)?|\/?>$/i],["atn",/^(?!style[\s=]|on)[a-z](?:[\w:-]*\w)?/i],["lang-uq.val",/^=\s*([^\s"'>]*(?:[^\s"'/>]|\/(?=\s)))/],["pun",/^[/<->]+/],["lang-js",/^on\w+\s*=\s*"([^"]+)"/i],["lang-js",/^on\w+\s*=\s*'([^']+)'/i],["lang-js",/^on\w+\s*=\s*([^\s"'>]+)/i],["lang-css",/^style\s*=\s*"([^"]+)"/i],["lang-css",/^style\s*=\s*'([^']+)'/i],["lang-css",
+/^style\s*=\s*([^\s"'>]+)/i]]),["in.tag"]);k(x([],[["atv",/^[\S\s]+/]]),["uq.val"]);k(u({keywords:F,hashComments:!0,cStyleComments:!0,types:K}),["c","cc","cpp","cxx","cyc","m"]);k(u({keywords:"null,true,false"}),["json"]);k(u({keywords:H,hashComments:!0,cStyleComments:!0,verbatimStrings:!0,types:K}),["cs"]);k(u({keywords:G,cStyleComments:!0}),["java"]);k(u({keywords:v,hashComments:!0,multiLineStrings:!0}),["bsh","csh","sh"]);k(u({keywords:I,hashComments:!0,multiLineStrings:!0,tripleQuotedStrings:!0}),
+["cv","py"]);k(u({keywords:"caller,delete,die,do,dump,elsif,eval,exit,foreach,for,goto,if,import,last,local,my,next,no,our,print,package,redo,require,sub,undef,unless,until,use,wantarray,while,BEGIN,END",hashComments:!0,multiLineStrings:!0,regexLiterals:!0}),["perl","pl","pm"]);k(u({keywords:J,hashComments:!0,multiLineStrings:!0,regexLiterals:!0}),["rb"]);k(u({keywords:w,cStyleComments:!0,regexLiterals:!0}),["js"]);k(u({keywords:"all,and,by,catch,class,else,extends,false,finally,for,if,in,is,isnt,loop,new,no,not,null,of,off,on,or,return,super,then,true,try,unless,until,when,while,yes",
+hashComments:3,cStyleComments:!0,multilineStrings:!0,tripleQuotedStrings:!0,regexLiterals:!0}),["coffee"]);k(x([],[["str",/^[\S\s]+/]]),["regex"]);window.prettyPrintOne=function(a,m,e){var h=document.createElement("PRE");h.innerHTML=a;e&&D(h,e);E({g:m,i:e,h:h});return h.innerHTML};window.prettyPrint=function(a){function m(){for(var e=window.PR_SHOULD_USE_CONTINUATION?l.now()+250:Infinity;p<h.length&&l.now()<e;p++){var n=h[p],k=n.className;if(k.indexOf("prettyprint")>=0){var k=k.match(g),f,b;if(b=
+!k){b=n;for(var o=void 0,c=b.firstChild;c;c=c.nextSibling)var i=c.nodeType,o=i===1?o?b:c:i===3?N.test(c.nodeValue)?b:o:o;b=(f=o===b?void 0:o)&&"CODE"===f.tagName}b&&(k=f.className.match(g));k&&(k=k[1]);b=!1;for(o=n.parentNode;o;o=o.parentNode)if((o.tagName==="pre"||o.tagName==="code"||o.tagName==="xmp")&&o.className&&o.className.indexOf("prettyprint")>=0){b=!0;break}b||((b=(b=n.className.match(/\blinenums\b(?::(\d+))?/))?b[1]&&b[1].length?+b[1]:!0:!1)&&D(n,b),d={g:k,h:n,i:b},E(d))}}p<h.length?setTimeout(m,
+250):a&&a()}for(var e=[document.getElementsByTagName("pre"),document.getElementsByTagName("code"),document.getElementsByTagName("xmp")],h=[],k=0;k<e.length;++k)for(var t=0,s=e[k].length;t<s;++t)h.push(e[k][t]);var e=q,l=Date;l.now||(l={now:function(){return+new Date}});var p=0,d,g=/\blang(?:uage)?-([\w.]+)(?!\S)/;m()};window.PR={createSimpleLexer:x,registerLangHandler:k,sourceDecorator:u,PR_ATTRIB_NAME:"atn",PR_ATTRIB_VALUE:"atv",PR_COMMENT:"com",PR_DECLARATION:"dec",PR_KEYWORD:"kwd",PR_LITERAL:"lit",
+PR_NOCODE:"nocode",PR_PLAIN:"pln",PR_PUNCTUATION:"pun",PR_SOURCE:"src",PR_STRING:"str",PR_TAG:"tag",PR_TYPE:"typ"}})();

api/''/styles/jsdoc-default.css

@@ -0,0 +1,740 @@
+@font-face {
+  font-family: 'webfont_din-regular';
+  src: url('https://docs.parseplatform.org/assets/fonts/din17sbop-regular-webfont.woff') format('woff');
+  font-weight: normal;
+  font-style: normal;
+}
+
+@font-face {
+  font-family: 'webfont_input';
+  src: url('https://docs.parseplatform.org/assets/fonts/d94de4bd-16a6-4c19-81bd-ed8f4e1624c6-3.woff') format('woff');
+  font-weight: normal;
+  font-style: normal;
+}
+
+@font-face {
+  font-family: 'webfont_alright';
+  src: url('https://docs.parseplatform.org/assets/fonts/ttfah-AlrightSubLPWebfontUseOnly-Light.woff') format('woff');
+  font-weight: 300;
+  font-style: normal;
+}
+
+@font-face {
+  font-family: 'webfont_alright';
+  src: url('https://docs.parseplatform.org/assets/fonts/ttfah-AlrightSubLPWebfontUseOnly-Regular.woff') format('woff');
+  font-weight: 400;
+  font-style: normal;
+}
+
+@font-face {
+  font-family: 'webfont_alright';
+  src: url('https://docs.parseplatform.org/assets/fonts/ttfah-AlrightSubLPWebfontUseOnly-Medium.woff') format('woff');
+  font-weight: 500;
+  font-style: normal;
+}
+
+@font-face {
+  font-family: 'webfont_alright';
+  src: url('https://docs.parseplatform.org/assets/fonts/ttfah-AlrightSubLPWebfontUseOnly-Bold.woff') format('woff');
+  font-weight: 700;
+  font-style: normal;
+}
+
+@font-face {
+  font-family: 'webfont_alright';
+  src: url('https://docs.parseplatform.org/assets/fonts/ttfah-AlrightSubLPWebfontUseOnly-Bold.woff') format('woff');
+  font-weight: 800;
+  font-style: normal;
+}
+
+
+* {
+  box-sizing: border-box
+}
+
+html, body {
+  height: 100%;
+  width: 100%;
+}
+
+body {
+  color: #4d4e53;
+  background-color: white;
+  margin: 0 auto;
+  padding: 0;
+  font-family: 'webfont_alright', Helvetica, sans-serif;
+  font-size: 16px;
+  line-height: 160%;
+}
+
+a,
+a:active {
+  color: #0095dd;
+  text-decoration: none;
+}
+
+a:hover {
+  text-decoration: underline
+}
+
+p, ul, ol, blockquote {
+  margin-bottom: 1em;
+}
+
+h1, h2, h3, h4, h5, h6 {
+  font-family: 'webfont_alright', 'Roboto', sans-serif;
+}
+
+h1, h2, h3, h4, h5, h6 {
+  color: #000;
+  font-weight: 400;
+  margin: 0;
+}
+
+h1 {
+  font-weight: 300;
+  font-size: 48px;
+  margin: 1em 0 .5em;
+}
+
+h1.page-title {margin-bottom: 10px;font-size: 34px;font-weight: 300;border-bottom: solid 2px #ddd;padding: .5em 0 .5em;margin-top: 0;}
+
+h2 {
+  font-size: 32px;
+  margin: 1.2em 0 .8em;
+  font-weight: bold;
+}
+
+h3 {
+  /* margin-top: 1em; */
+  /* margin-bottom: 16px; */
+  /* font-weight: bold; */
+  padding: 0;
+  margin: 1em 0 .6em;
+  font-size: 28px;
+  /* border-bottom: 1px solid #eee; */
+  /* padding-bottom: 15px; */
+}
+
+h4 {
+  font-size: 18px;
+  margin: 1em 0 .2em;
+  color: #4d4e53;
+  /* border-bottom: 1px solid #eee; */
+  padding-bottom: 8px;
+}
+
+h5, .container-overview .subsection-title {
+  font-size: 120%;
+  /* letter-spacing: -0.01em; */
+  margin: 20px 0 5px;
+}
+
+h6 {
+  font-size: 100%;
+  letter-spacing: -0.01em;
+  margin: 6px 0 3px 0;
+  font-style: italic;
+}
+
+tt, code, kbd, samp {
+  font-family: 'webfont_input', Consolas, Monaco, 'Andale Mono', monospace;
+  background: #f4f4f4;
+  padding: 1px 5px;
+  border-radius: 5px;
+  font-size: 14px;
+}
+
+blockquote {
+  display: block;
+  border-left: 4px solid #eee;
+  margin: 0;
+  padding-left: 1em;
+  color: #888;
+}
+
+.class-description {
+  font-size: 130%;
+  line-height: 140%;
+  margin-bottom: 1em;
+  margin-top: 1em;
+}
+
+.class-description:empty {
+  margin: 0
+}
+
+/** Container **/
+#main {
+  float: right;
+  min-width: 360px;
+  width: calc(100% - 250px);
+  padding: 0 30px 20px 30px;
+}
+
+header {
+  display: block
+}
+
+section {
+  display: block;
+  background-color: #fff;
+  padding: 0;
+}
+
+.variation {
+  display: none
+}
+
+.signature-attributes {
+  font-size: 60%;
+  color: #aaa;
+  font-style: italic;
+  font-weight: lighter;
+}
+
+/** Readme  **/
+
+.readme {
+  font-size: 16px;
+}
+
+.readme h1,
+.readme h2,
+.readme h3,
+.readme h4,
+.readme h5 {
+  margin-top: 1em;
+  margin-bottom: 16px;
+  font-weight: bold;
+  padding: 0;
+}
+
+.readme h1 {
+  font-size: 2em;
+  padding-bottom: 0.3em;
+}
+
+.readme h2 {
+  font-size: 1.75em;
+  padding-bottom: 0.3em;
+}
+
+.readme h3 {
+  font-size: 1.5em;
+  background-color: transparent;
+}
+
+.readme h4 {
+  font-size: 1.25em;
+}
+
+.readme h5 {
+  font-size: 1em;
+}
+
+.readme img {
+  max-width: 100%;
+}
+
+.readme ul, .readme ol {
+  padding-left: 2em;
+}
+
+.readme pre > code {
+  font-size: 0.85em;
+}
+
+.readme table {
+  margin-bottom: 1em;
+  border-collapse: collapse;
+  border-spacing: 0;
+}
+
+.readme table tr {
+  background-color: #fff;
+  border-top: 1px solid #ccc;
+}
+
+.readme table th,
+.readme table td {
+  padding: 6px 13px;
+  border: 1px solid #ddd;
+}
+
+.readme table tr:nth-child(2n) {
+  background-color: #f8f8f8;
+}
+
+/** Nav **/
+nav {
+  float: left;
+  display: block;
+  width: 280px;
+  background: #fff;
+  overflow: auto;
+  position: fixed;
+  height: 100%;
+  padding: 10px;
+  border-right: 1px solid #eee;
+  /* box-shadow: 0 0 3px rgba(0,0,0,0.1); */
+}
+
+nav li {
+  list-style: none;
+  padding: 0;
+  margin: 0;
+}
+
+.nav-heading {
+  margin-top: 10px;
+  font-weight: bold;
+}
+
+.nav-heading a {
+  color: #888;
+  font-size: 14px;
+  display: inline-block;
+}
+
+.nav-item-type {
+  /* margin-left: 5px; */
+  width: 18px;
+  height: 18px;
+  display: inline-block;
+  text-align: center;
+  border-radius: 0.2em;
+  margin-right: 5px;
+  font-weight: bold;
+  line-height: 20px;
+  font-size: 13px;
+}
+
+.type-function {
+  background: #B3E5FC;
+  color: #0288D1;
+}
+
+.type-class {
+  background: #D1C4E9;
+  color: #4527A0;
+}
+
+.type-member {
+  background: #C8E6C9;
+  color: #388E3C;
+}
+
+.type-module {
+  background: #E1BEE7;
+  color: #7B1FA2;
+}
+
+
+/** Footer **/
+footer {
+  color: hsl(0, 0%, 28%);
+  margin-left: 250px;
+  display: block;
+  padding: 30px;
+  font-style: italic;
+  font-size: 90%;
+  border-top: 1px solid #eee;
+}
+
+.ancestors {
+  color: #999
+}
+
+.ancestors a {
+   color: #999 !important;
+   text-decoration: none;
+}
+
+.clear {
+  clear: both
+}
+
+.important {
+  font-weight: bold;
+  color: #950B02;
+}
+
+.yes-def {
+  text-indent: -1000px
+}
+
+.type-signature {
+  color: #aaa
+}
+
+.name, .signature {
+  font-family: 'webfont_input', Consolas, Monaco, 'Andale Mono', monospace
+}
+
+.details {
+  margin-top: 14px;
+  border-left: 2px solid #DDD;
+  line-height: 30px;
+}
+
+.details dt {
+   width: 120px;
+   float: left;
+   padding-left: 10px;
+}
+
+.details dd {
+   margin-left: 70px
+}
+
+.details ul {
+   margin: 0
+}
+
+.details ul {
+   list-style-type: none
+}
+
+.details li {
+   margin-left: 30px
+}
+
+.details pre.prettyprint {
+   margin: 0
+}
+
+.details .object-value {
+   padding-top: 0
+}
+
+.description {
+  margin-bottom: 1em;
+  margin-top: 1em;
+}
+
+.code-caption {
+  font-style: italic;
+  font-size: 107%;
+  margin: 0;
+}
+
+.prettyprint {
+  font-size: 13px;
+  border: 1px solid #ddd;
+  border-radius: 3px;
+  box-shadow: 0 1px 3px hsla(0, 0%, 0%, 0.05);
+  overflow: auto;
+}
+
+.prettyprint.source {
+  width: inherit
+}
+
+.prettyprint code {
+  font-size: 12px;
+  line-height: 18px;
+  display: block;
+  background-color: #fff;
+  color: #4D4E53;
+}
+
+.prettyprint code:empty:before {
+  content: '';
+}
+
+.prettyprint > code {
+  padding: 15px
+}
+
+.prettyprint .linenums code {
+  padding: 0 15px
+}
+
+.prettyprint .linenums li:first-of-type code {
+  padding-top: 15px
+}
+
+.prettyprint code span.line {
+  display: inline-block
+}
+
+.prettyprint.linenums {
+  padding-left: 70px;
+  -webkit-user-select: none;
+  -moz-user-select: none;
+  -ms-user-select: none;
+  user-select: none;
+}
+
+.prettyprint.linenums ol {
+   padding-left: 0
+}
+
+.prettyprint.linenums li {
+   border-left: 3px #ddd solid
+}
+
+.prettyprint.linenums li.selected, .prettyprint.linenums li.selected * {
+   background-color: lightyellow
+}
+
+.prettyprint.linenums li * {
+   -webkit-user-select: text;
+   -moz-user-select: text;
+   -ms-user-select: text;
+   user-select: text;
+}
+
+.params, .props {
+  border-spacing: 0;
+  border: 1px solid #ddd;
+  border-collapse: collapse;
+  border-radius: 3px;
+  box-shadow: 0 1px 3px rgba(0,0,0,0.1);
+  width: 100%;
+  font-size: 14px;
+  /* margin-left: 15px; */
+}
+
+.params .name, .props .name, .name code {
+   color: #4D4E53;
+   font-family: 'webfont_input', Consolas, Monaco, 'Andale Mono', monospace;
+   font-size: 100%;
+}
+
+.params td, .params th, .props td, .props th {
+   margin: 0px;
+   text-align: left;
+   vertical-align: top;
+   padding: 10px;
+   display: table-cell;
+}
+
+.params td {
+   border-top: 1px solid #eee
+}
+
+.params thead tr, .props thead tr {
+   background-color: #fff;
+   font-weight: bold;
+}
+
+.params .params thead tr, .props .props thead tr {
+   background-color: #fff;
+   font-weight: bold;
+}
+
+.params td.description > p:first-child, .props td.description > p:first-child {
+   margin-top: 0;
+   padding-top: 0;
+}
+
+.params td.description > p:last-child, .props td.description > p:last-child {
+   margin-bottom: 0;
+   padding-bottom: 0;
+}
+
+dl.param-type {
+  /* border-bottom: 1px solid hsl(0, 0%, 87%); */
+  margin: 0;
+  padding: 0;
+  font-size: 16px;
+}
+
+.param-type dt, .param-type dd {
+  display: inline-block
+}
+
+.param-type dd {
+  font-family: 'webfont_input';
+  display: inline-block;
+  padding: 0;
+  margin: 0;
+  font-size: 14px;
+}
+
+.disabled {
+  color: #454545
+}
+
+/* navicon button */
+.navicon-button {
+  display: none;
+  position: relative;
+  padding: 2.0625rem 1.5rem;
+  transition: 0.25s;
+  cursor: pointer;
+  user-select: none;
+  opacity: .8;
+}
+.navicon-button .navicon:before, .navicon-button .navicon:after {
+  transition: 0.25s;
+}
+.navicon-button:hover {
+  transition: 0.5s;
+  opacity: 1;
+}
+.navicon-button:hover .navicon:before, .navicon-button:hover .navicon:after {
+  transition: 0.25s;
+}
+.navicon-button:hover .navicon:before {
+  top: .825rem;
+}
+.navicon-button:hover .navicon:after {
+  top: -.825rem;
+}
+
+/* navicon */
+.navicon {
+  position: relative;
+  width: 2.5em;
+  height: .3125rem;
+  background: #000;
+  transition: 0.3s;
+  border-radius: 2.5rem;
+}
+.navicon:before, .navicon:after {
+  display: block;
+  content: "";
+  height: .3125rem;
+  width: 2.5rem;
+  background: #000;
+  position: absolute;
+  z-index: -1;
+  transition: 0.3s 0.25s;
+  border-radius: 1rem;
+}
+.navicon:before {
+  top: .625rem;
+}
+.navicon:after {
+  top: -.625rem;
+}
+
+/* open */
+.nav-trigger:checked + label:not(.steps) .navicon:before,
+.nav-trigger:checked + label:not(.steps) .navicon:after {
+  top: 0 !important;
+}
+
+.nav-trigger:checked + label .navicon:before,
+.nav-trigger:checked + label .navicon:after {
+  transition: 0.5s;
+}
+
+/* Minus */
+.nav-trigger:checked + label {
+  transform: scale(0.75);
+}
+
+/* × and + */
+.nav-trigger:checked + label.plus .navicon,
+.nav-trigger:checked + label.x .navicon {
+  background: transparent;
+}
+
+.nav-trigger:checked + label.plus .navicon:before,
+.nav-trigger:checked + label.x .navicon:before {
+  transform: rotate(-45deg);
+  background: #FFF;
+}
+
+.nav-trigger:checked + label.plus .navicon:after,
+.nav-trigger:checked + label.x .navicon:after {
+  transform: rotate(45deg);
+  background: #FFF;
+}
+
+.nav-trigger:checked + label.plus {
+  transform: scale(0.75) rotate(45deg);
+}
+
+.nav-trigger:checked ~ nav {
+  left: 0 !important;
+}
+
+.nav-trigger:checked ~ .overlay {
+  display: block;
+}
+
+.nav-trigger {
+  position: fixed;
+  top: 0;
+  clip: rect(0, 0, 0, 0);
+}
+
+.overlay {
+  display: none;
+  position: fixed;
+  top: 0;
+  bottom: 0;
+  left: 0;
+  right: 0;
+  width: 100%;
+  height: 100%;
+  background: hsla(0, 0%, 0%, 0.5);
+  z-index: 1;
+}
+
+.section-method {
+  margin-bottom: 30px;
+  padding-bottom: 30px;
+  border-bottom: 1px solid #eee;
+}
+
+@media only screen and (min-width: 320px) and (max-width: 680px) {
+  body {
+    overflow-x: hidden;
+  }
+
+  nav {
+    background: #FFF;
+    width: 250px;
+    height: 100%;
+    position: fixed;
+    top: 0;
+    right: 0;
+    bottom: 0;
+    left: -250px;
+    z-index: 3;
+    padding: 0 10px;
+    transition: left 0.2s;
+  }
+
+  .navicon-button {
+    display: inline-block;
+    position: fixed;
+    top: 1.5em;
+    right: 0;
+    z-index: 2;
+  }
+
+  #main {
+    width: 100%;
+    min-width: 360px;
+  }
+
+  #main h1.page-title {
+    margin: 1em 0;
+  }
+
+  #main section {
+    padding: 0;
+  }
+
+  footer {
+    margin-left: 0;
+  }
+}
+
+@media only print {
+  nav {
+    display: none;
+  }
+
+  #main {
+    float: none;
+    width: 100%;
+  }
+}

api/''/styles/prettify-jsdoc.css

@@ -0,0 +1,111 @@
+/* JSDoc prettify.js theme */
+
+/* plain text */
+.pln {
+  color: #000000;
+  font-weight: normal;
+  font-style: normal;
+}
+
+/* string content */
+.str {
+  color: hsl(104, 100%, 24%);
+  font-weight: normal;
+  font-style: normal;
+}
+
+/* a keyword */
+.kwd {
+  color: #000000;
+  font-weight: bold;
+  font-style: normal;
+}
+
+/* a comment */
+.com {
+  font-weight: normal;
+  font-style: italic;
+}
+
+/* a type name */
+.typ {
+  color: #000000;
+  font-weight: normal;
+  font-style: normal;
+}
+
+/* a literal value */
+.lit {
+  color: #006400;
+  font-weight: normal;
+  font-style: normal;
+}
+
+/* punctuation */
+.pun {
+  color: #000000;
+  font-weight: bold;
+  font-style: normal;
+}
+
+/* lisp open bracket */
+.opn {
+  color: #000000;
+  font-weight: bold;
+  font-style: normal;
+}
+
+/* lisp close bracket */
+.clo {
+  color: #000000;
+  font-weight: bold;
+  font-style: normal;
+}
+
+/* a markup tag name */
+.tag {
+  color: #006400;
+  font-weight: normal;
+  font-style: normal;
+}
+
+/* a markup attribute name */
+.atn {
+  color: #006400;
+  font-weight: normal;
+  font-style: normal;
+}
+
+/* a markup attribute value */
+.atv {
+  color: #006400;
+  font-weight: normal;
+  font-style: normal;
+}
+
+/* a declaration */
+.dec {
+  color: #000000;
+  font-weight: bold;
+  font-style: normal;
+}
+
+/* a variable name */
+.var {
+  color: #000000;
+  font-weight: normal;
+  font-style: normal;
+}
+
+/* a function name */
+.fun {
+  color: #000000;
+  font-weight: bold;
+  font-style: normal;
+}
+
+/* Specify class=linenums on a pre to get line numbering */
+ol.linenums {
+  margin-top: 0;
+  margin-bottom: 0;
+}

api/''/styles/prettify-tomorrow.css

@@ -0,0 +1,132 @@
+/* Tomorrow Theme */
+/* Original theme - https://github.com/chriskempson/tomorrow-theme */
+/* Pretty printing styles. Used with prettify.js. */
+/* SPAN elements with the classes below are added by prettyprint. */
+/* plain text */
+.pln {
+  color: #4d4d4c; }
+
+@media screen {
+  /* string content */
+  .str {
+    color: hsl(104, 100%, 24%); }
+
+  /* a keyword */
+  .kwd {
+    color: hsl(240, 100%, 50%); }
+
+  /* a comment */
+  .com {
+    color: hsl(0, 0%, 60%); }
+
+  /* a type name */
+  .typ {
+    color: hsl(240, 100%, 32%); }
+
+  /* a literal value */
+  .lit {
+    color: hsl(240, 100%, 40%); }
+
+  /* punctuation */
+  .pun {
+    color: #000000; }
+
+  /* lisp open bracket */
+  .opn {
+    color: #000000; }
+
+  /* lisp close bracket */
+  .clo {
+    color: #000000; }
+
+  /* a markup tag name */
+  .tag {
+    color: #c82829; }
+
+  /* a markup attribute name */
+  .atn {
+    color: #f5871f; }
+
+  /* a markup attribute value */
+  .atv {
+    color: #3e999f; }
+
+  /* a declaration */
+  .dec {
+    color: #f5871f; }
+
+  /* a variable name */
+  .var {
+    color: #c82829; }
+
+  /* a function name */
+  .fun {
+    color: #4271ae; } }
+/* Use higher contrast and text-weight for printable form. */
+@media print, projection {
+  .str {
+    color: #060; }
+
+  .kwd {
+    color: #006;
+    font-weight: bold; }
+
+  .com {
+    color: #600;
+    font-style: italic; }
+
+  .typ {
+    color: #404;
+    font-weight: bold; }
+
+  .lit {
+    color: #044; }
+
+  .pun, .opn, .clo {
+    color: #440; }
+
+  .tag {
+    color: #006;
+    font-weight: bold; }
+
+  .atn {
+    color: #404; }
+
+  .atv {
+    color: #060; } }
+/* Style */
+/*
+pre.prettyprint {
+  background: white;
+  font-family: Consolas, Monaco, 'Andale Mono', monospace;
+  font-size: 12px;
+  line-height: 1.5;
+  border: 1px solid #ccc;
+  padding: 10px; }
+*/
+
+/* Specify class=linenums on a pre to get line numbering */
+ol.linenums {
+  margin-top: 0;
+  margin-bottom: 0; }
+
+/* IE indents via margin-left */
+li.L0,
+li.L1,
+li.L2,
+li.L3,
+li.L4,
+li.L5,
+li.L6,
+li.L7,
+li.L8,
+li.L9 {
+  /* */ }
+
+/* Alternate shading for lines */
+li.L1,
+li.L3,
+li.L5,
+li.L7,
+li.L9 {
+  /* */ }

api/3.1.0/scripts/linenumber.js

@@ -0,0 +1,25 @@
+/*global document */
+(function() {
+    var source = document.getElementsByClassName('prettyprint source linenums');
+    var i = 0;
+    var lineNumber = 0;
+    var lineId;
+    var lines;
+    var totalLines;
+    var anchorHash;
+
+    if (source && source[0]) {
+        anchorHash = document.location.hash.substring(1);
+        lines = source[0].getElementsByTagName('li');
+        totalLines = lines.length;
+
+        for (; i < totalLines; i++) {
+            lineNumber++;
+            lineId = 'line' + lineNumber;
+            lines[i].id = lineId;
+            if (lineId === anchorHash) {
+                lines[i].className += ' selected';
+            }
+        }
+    }
+})();