zerobounce-sdk 2.1.8 → 2.2.0

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: zerobounce-sdk
 version: !ruby/object:Gem::Version
-  version: 2.1.8
+  version: 2.2.0
 platform: ruby
 authors:
 - Zero Bounce
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2026-08-14 00:00:00.000000000 Z
+date: 2026-11-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rest-client
@@ -31,7 +31,7 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '0'
-  type: :runtime
+  type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
@@ -289,52 +289,27 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".dockerignore"
-- ".env.example"
-- ".github/auto_assign.yml"
-- ".github/dependabot.yml"
-- ".github/workflows/auto_assign_ci.yaml"
-- ".github/workflows/codeql.yml"
-- ".github/workflows/publish.yml"
-- ".github/workflows/sdk_ci.yml"
-- ".gitignore"
-- ".rspec"
-- ".ruby-version"
 - CHANGELOG.md
-- CODE_OF_CONDUCT.md
-- CONTRIBUTING.md
-- Dockerfile
-- Gemfile
-- Gemfile.lock
 - LICENSE
 - LICENSE.txt
 - README.md
-- Rakefile
-- SECURITY.md
-- bin/bundle
-- bin/console
-- bin/setup
-- data/zerobounce-ai-scoring.csv
-- data/zerobounce-batch-validation.csv
-- documentation.md
-- files/scoring.csv
-- files/validation.csv
-- files/zerobounce-ai-scoring.csv
-- files/zerobounce-batch-validation.csv
 - lib/zerobounce.rb
 - lib/zerobounce/api_urls.rb
 - lib/zerobounce/base_request.rb
+- lib/zerobounce/client.rb
 - lib/zerobounce/configuration.rb
 - lib/zerobounce/download_type.rb
 - lib/zerobounce/error.rb
 - lib/zerobounce/get_file_helper.rb
 - lib/zerobounce/get_file_options.rb
 - lib/zerobounce/mock_request.rb
+- lib/zerobounce/priority3.rb
 - lib/zerobounce/request.rb
+- lib/zerobounce/response_error.rb
 - lib/zerobounce/validate_status.rb
 - lib/zerobounce/validate_sub_status.rb
 - lib/zerobounce/version.rb
-- zerobounce.gemspec
+- lib/zerobounce/warmup.rb
 homepage: https://zerobounce.net
 licenses:
 - MIT
@@ -348,7 +323,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: '2.5'
+      version: '3.0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="

data/.dockerignore

@@ -1,17 +0,0 @@
-# Keep .git so gemspec `git ls-files` works during `bundle install` in the image.
-
-# Docs and tooling not needed to run specs in the image
-*.md
-documentation*.md
-.spec
-.rspec_status
-coverage/
-tmp/
-pkg/
-vendor/bundle
-
-# OS & env
-.DS_Store
-Thumbs.db
-.env
-.env.*

data/.env.example

@@ -1,3 +0,0 @@
-# ZeroBounce API key (standard). Get your key at https://www.zerobounce.net/docs/api-dashboard
-# Copy this file to .env and set your key.
-ZEROBOUNCE_API_KEY=your_api_key_here

data/.github/auto_assign.yml

@@ -1,5 +0,0 @@
-addReviewers: false
-addAssignees: true
-assignees:
-  - franciscbalint
-numberOfAssignees: 1

data/.github/dependabot.yml

@@ -1,35 +0,0 @@
-# To get started with Dependabot version updates, you'll need to specify which
-# package ecosystems to update and where the package manifests are located.
-# https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#versioning-strategy
-
-version: 2
-updates:
-  # Keep the Ruby dependencies up to date
-  - package-ecosystem: "bundler"
-    directory: "/"
-    schedule:
-      interval: "weekly"
-      day: "monday"
-    target-branch: "develop"
-    labels:
-      - "ruby dependencies"
-    groups:
-      bundler:
-        applies-to: version-updates
-        patterns:
-          - "*"
-
-  # Keep the Github Actions dependencies up to date
-  - package-ecosystem: "github-actions"
-    directory: "/"
-    schedule:
-      interval: "weekly"
-      day: "monday"
-    target-branch: "develop"
-    labels:
-      - "github dependencies"
-    groups:
-      github:
-        applies-to: version-updates
-        patterns:
-          - "*"

data/.github/workflows/auto_assign_ci.yaml

@@ -1,21 +0,0 @@
-name: Auto Assign
-
-on:
-  pull_request_target:
-    types:
-      - opened
-      - synchronize
-      - reopened
-
-permissions:
-  contents: read
-  pull-requests: write
-
-jobs:
-  add-assignee:
-    name: Auto assign (me only)
-    runs-on: ubuntu-latest
-    steps:
-      - uses: kentaro-m/auto-assign-action@v2.0.2
-        with:
-          configuration-path: ".github/auto_assign.yml"

data/.github/workflows/codeql.yml

@@ -1,105 +0,0 @@
-# For most projects, this workflow file will not need changing; you simply need
-# to commit it to your repository.
-#
-# You may wish to alter this file to override the set of languages analyzed,
-# or to provide custom queries or build logic.
-#
-# ******** NOTE ********
-# We have attempted to detect the languages in your repository. Please check
-# the `language` matrix defined below to confirm you have the correct set of
-# supported CodeQL languages.
-#
-name: "CodeQL Advanced"
-
-on:
-  push:
-    branches: [ "develop" ]
-  pull_request:
-    branches: [ "develop" ]
-  schedule:
-    - cron: '19 14 * * 4'
-
-permissions:
-  security-events: write
-  packages: read
-  actions: read
-  contents: read
-
-jobs:
-  analyze:
-    name: Analyze (${{ matrix.language }})
-    # Runner size impacts CodeQL analysis time. To learn more, please see:
-    #   - https://gh.io/recommended-hardware-resources-for-running-codeql
-    #   - https://gh.io/supported-runners-and-hardware-resources
-    #   - https://gh.io/using-larger-runners (GitHub.com only)
-    # Consider using larger runners or machines with greater resources for possible analysis time improvements.
-    runs-on: ${{ (matrix.language == 'swift' && 'macos-latest') || 'ubuntu-latest' }}
-    permissions:
-      # required for all workflows
-      security-events: write
-
-      # required to fetch internal or private CodeQL packs
-      packages: read
-
-      # only required for workflows in private repositories
-      actions: read
-      contents: read
-
-    strategy:
-      fail-fast: false
-      matrix:
-        include:
-        - language: ruby
-          build-mode: none
-        # CodeQL supports the following values keywords for 'language': 'actions', 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'rust', 'swift'
-        # Use `c-cpp` to analyze code written in C, C++ or both
-        # Use 'java-kotlin' to analyze code written in Java, Kotlin or both
-        # Use 'javascript-typescript' to analyze code written in JavaScript, TypeScript or both
-        # To learn more about changing the languages that are analyzed or customizing the build mode for your analysis,
-        # see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.
-        # If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize how
-        # your codebase is analyzed, see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages
-    steps:
-    - name: Checkout repository
-      uses: actions/checkout@v7
-
-    # Add any setup steps before running the `github/codeql-action/init` action.
-    # This includes steps like installing compilers or runtimes (`actions/setup-node`
-    # or others). This is typically only required for manual builds.
-    # - name: Setup runtime (example)
-    #   uses: actions/setup-example@v1
-
-    # Initializes the CodeQL tools for scanning.
-    - name: Initialize CodeQL
-      uses: github/codeql-action/init@v4.36.3
-      with:
-        languages: ${{ matrix.language }}
-        build-mode: ${{ matrix.build-mode }}
-        # If you wish to specify custom queries, you can do so here or in a config file.
-        # By default, queries listed here will override any specified in a config file.
-        # Prefix the list here with "+" to use these queries and those in the config file.
-
-        # For more details on CodeQL's query packs, refer to: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
-        # queries: security-extended,security-and-quality
-
-    # If the analyze step fails for one of the languages you are analyzing with
-    # "We were unable to automatically build your code", modify the matrix above
-    # to set the build mode to "manual" for that language. Then modify this step
-    # to build your code.
-    # ℹ️ Command-line programs to run using the OS shell.
-    # 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
-    - name: Run manual build steps
-      if: matrix.build-mode == 'manual'
-      shell: bash
-      run: |
-        echo 'If you are using a "manual" build mode for one or more of the' \
-          'languages you are analyzing, replace this with the commands to build' \
-          'your code, for example:'
-        echo '  make bootstrap'
-        echo '  make release'
-        exit 1
-
-    - name: Perform CodeQL Analysis
-      uses: github/codeql-action/analyze@v4.36.3
-      with:
-        category: "/language:${{matrix.language}}"

data/.github/workflows/publish.yml

@@ -1,131 +0,0 @@
-name: Publish
-
-on:
-  workflow_dispatch:
-    inputs:
-      tag:
-        type: string
-        description: Tag to publish (e.g. v2.1.5)
-        required: true
-
-permissions:
-  contents: read
-
-jobs:
-  validate-tag:
-    name: Validate tag
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v7
-        with:
-          fetch-depth: 0
-          ref: ${{ github.event.inputs.tag }}
-
-      - name: Verify tag and gem version
-        run: |
-          TAG="${{ github.event.inputs.tag }}"
-          if [ -z "$TAG" ]; then
-            echo "Error: Tag is required."
-            exit 1
-          fi
-          if ! git rev-parse "$TAG" >/dev/null 2>&1; then
-            echo "Error: Tag '$TAG' does not exist."
-            exit 1
-          fi
-          TAG_VERSION="${TAG#v}"
-          PKG_VERSION=$(grep -E "VERSION\s*=" lib/zerobounce/version.rb | sed -E "s/.*'([^']+)'.*/\1/")
-          if [ -z "$PKG_VERSION" ]; then
-            echo "Error: Could not read version from lib/zerobounce/version.rb"
-            exit 1
-          fi
-          if [ "$PKG_VERSION" != "$TAG_VERSION" ]; then
-            echo "Error: lib/zerobounce/version.rb ($PKG_VERSION) does not match tag ($TAG)."
-            exit 1
-          fi
-          echo "Publishing tag: $TAG (zerobounce-sdk@$PKG_VERSION)"
-
-  test:
-    name: Test
-    needs: [validate-tag]
-    if: ${{ !cancelled() && !contains(needs.*.result, 'failure') && !contains(needs.*.result, 'cancelled') }}
-    runs-on: ubuntu-latest
-    env:
-      ZEROBOUNCE_API_KEY: "invalid_key_for_tests"
-    steps:
-      - name: Checkout tag
-        uses: actions/checkout@v7
-        with:
-          ref: ${{ github.event.inputs.tag }}
-
-      - name: Set up Ruby
-        uses: ruby/setup-ruby@v1
-        with:
-          ruby-version: "3.2"
-          bundler-cache: true
-
-      - name: Run specs
-        run: bundle exec rspec
-
-  publish:
-    name: Build and publish to RubyGems
-    needs: [test]
-    if: ${{ !cancelled() && !failure() }}
-    runs-on: ubuntu-latest
-    environment: release
-    permissions:
-      id-token: write
-      contents: read
-    steps:
-      - name: Checkout tag
-        uses: actions/checkout@v7
-        with:
-          ref: ${{ github.event.inputs.tag }}
-
-      - name: Set up Ruby
-        uses: ruby/setup-ruby@v1
-        with:
-          ruby-version: "3.2"
-          bundler-cache: true
-
-      - name: Configure RubyGems credentials
-        uses: rubygems/configure-rubygems-credentials@main
-        with:
-          api-token: ${{ secrets.RUBYGEMS_API_TOKEN }}
-
-      - name: Build gem
-        run: gem build zerobounce.gemspec
-
-      - name: Publish to RubyGems
-        run: |
-          GEM_FILE=$(ls zerobounce-sdk-*.gem)
-          echo "Pushing $GEM_FILE"
-          gem push "$GEM_FILE"
-
-  release:
-    name: Create GitHub Release
-    needs: [publish]
-    if: ${{ !cancelled() && !failure() }}
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v7
-        with:
-          ref: ${{ github.event.inputs.tag }}
-          fetch-depth: 0
-
-      - name: Create release if missing
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          TAG="${{ github.event.inputs.tag }}"
-          if gh release view "$TAG" --repo "${{ github.repository }}" >/dev/null 2>&1; then
-            echo "Release $TAG already exists, skipping."
-          else
-            gh release create "$TAG" \
-              --repo "${{ github.repository }}" \
-              --title "$TAG" \
-              --generate-notes
-          fi

data/.github/workflows/sdk_ci.yml

@@ -1,29 +0,0 @@
-# Run RSpec tests (VCR cassettes; no live API key needed for recorded specs).
-name: SDK CI
-
-on:
-  pull_request:
-    types: [opened, synchronize, reopened]
-  push:
-    branches: [main, master]
-
-permissions:
-  contents: read
-
-jobs:
-  test:
-    name: Test
-    runs-on: ubuntu-latest
-    env:
-      ZEROBOUNCE_API_KEY: "invalid_key_for_tests"
-    steps:
-      - uses: actions/checkout@v7
-
-      - name: Set up Ruby
-        uses: ruby/setup-ruby@v1
-        with:
-          ruby-version: "3.2"
-          bundler-cache: true
-
-      - name: Run specs
-        run: bundle exec rspec

data/.gitignore

@@ -1,70 +0,0 @@
-*.gem
-*.rbc
-/.config
-/coverage/
-/InstalledFiles
-/pkg/
-/spec/reports/
-/spec/examples.txt
-/test/tmp/
-/test/version_tmp/
-/tmp/
-
-# Used by dotenv library to load environment variables.
-.env
-
-# Ignore Byebug command history file.
-.byebug_history
-
-## Specific to RubyMotion:
-.dat*
-.repl_history
-build/
-*.bridgesupport
-build-iPhoneOS/
-build-iPhoneSimulator/
-
-## Specific to RubyMotion (use of CocoaPods):
-#
-# We recommend against adding the Pods directory to your .gitignore. However
-# you should judge for yourself, the pros and cons are mentioned at:
-# https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control
-#
-# vendor/Pods/
-
-## Documentation cache and generated files:
-/.yardoc/
-/_yardoc/
-/doc/
-/rdoc/
-
-## Environment normalization:
-/.bundle/
-/vendor/bundle
-/lib/bundler/man/
-
-# for a library or gem, you might want to ignore these files since the code is
-# intended to run in multiple environments; otherwise, check them in:
-# Gemfile.lock
-# .ruby-version
-# .ruby-gemset
-
-# unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
-.rvmrc
-
-# Used by RuboCop. Remote config files pulled in from inherit_from directive.
-# .rubocop-https?--*
-
-# Used by RSpec
-.rspec_status
-
-
-# Log files
-output.err
-output.log
-
-.DS_Store
-Thumbs.db
-.idea/
-.cursor/
-.env

data/.rspec

@@ -1,2 +0,0 @@
---require spec_helper
---format progress

data/.ruby-version

@@ -1 +0,0 @@
-3.2.1

data/CODE_OF_CONDUCT.md

@@ -1,69 +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 to the project team at **integrations@zerobounce.net**. All complaints will be reviewed and investigated promptly and fairly. The project team is obligated to maintain confidentiality with regard to the reporter of an incident.
-
-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/