upgrade to 1.0.6

Author: CodeWithSushil

.env.example

@@ -0,0 +1,7 @@
+# Supabase Config
+
+# Supabase database URL
+SB_URL=https://[your].supabase.co
+
+# Supabase Anon or `service_role` API key.
+SB_APIKEY= your anon api key

.github/FUNDING.yml

@@ -0,0 +1,15 @@
+# These are supported funding model platforms
+
+github: Ashishkumbhar01
+patreon: Code_With_Sushil
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+polar: # Replace with a single Polar username
+buy_me_a_coffee: # Replace with a single Buy Me a Coffee username
+thanks_dev: # Replace with a single thanks.dev username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

.github/SECURITY.md

@@ -0,0 +1,21 @@
+# Security Policy
+
+## Supported Versions
+
+Use this section to tell people about which versions of your project are
+currently being supported with security updates.
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 5.1.x   | :white_check_mark: |
+| 5.0.x   | :x:                |
+| 4.0.x   | :white_check_mark: |
+| < 4.0   | :x:                |
+
+## Reporting a Vulnerability
+
+Use this section to tell people how to report a vulnerability.
+
+Tell them where to go, how often they can expect to get an update on a
+reported vulnerability, what to expect if the vulnerability is accepted or
+declined, etc.

.github/dependabot.yml

@@ -0,0 +1,27 @@
+# Rule
+version: 2
+updates:
+  # This section defines updates for Composer dependencies
+  - package-ecosystem: "composer"
+    # Directory where the Composer file is located
+    directory: "/"
+    # Frequency of the updates (daily, weekly, monthly)
+    schedule:
+      interval: "weekly"
+    # Optionally, you can set a time for the updates
+    # time: "08:00"
+    # Optionally, set a day for weekly updates (monday, tuesday, etc.)
+    # day: "monday"
+    # Optionally, ignore certain dependencies or versions
+    # ignore:
+    #   - dependency-name: "vendor/package"
+    #     versions: ["1.x", "2.0.0"]
+    # Optionally, configure the behavior of pull requests
+    pull-request-branch-name:
+      separator: "_"
+    commit-message:
+      prefix: "dependabot:"
+      include: "scope"
+    target-branch: "master"
+    versioning-strategy: "increase"
+    rebase-strategy: "auto"

.github/workflows/dependency-review.yml

@@ -0,0 +1,39 @@
+# Dependency Review Action
+#
+# This Action will scan dependency manifest files that change as part of a Pull Request,
+# surfacing known-vulnerable versions of the packages declared or updated in the PR.
+# Once installed, if the workflow run is marked as required, PRs introducing known-vulnerable
+# packages will be blocked from merging.
+#
+# Source repository: https://github.com/actions/dependency-review-action
+# Public documentation: https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#dependency-review-enforcement
+name: 'Dependency review'
+on:
+  pull_request:
+    branches: [ "master" ]
+
+# If using a dependency submission action in this workflow this permission will need to be set to:
+#
+# permissions:
+#   contents: write
+#
+# https://docs.github.com/en/enterprise-cloud@latest/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api
+permissions:
+  contents: read
+  # Write permissions for pull-requests are required for using the `comment-summary-in-pr` option, comment out if you aren't using this option
+  pull-requests: write
+
+jobs:
+  dependency-review:
+    runs-on: ubuntu-latest
+    steps:
+      - name: 'Checkout repository'
+        uses: actions/checkout@v4
+      - name: 'Dependency Review'
+        uses: actions/dependency-review-action@v4
+        # Commonly enabled options, see https://github.com/actions/dependency-review-action#configuration-options for all available options.
+        with:
+          comment-summary-in-pr: always
+        #   fail-on-severity: moderate
+        #   deny-licenses: GPL-1.0-or-later, LGPL-2.0-or-later
+        #   retry-on-snapshot-warnings: true

.github/workflows/label.yml

@@ -0,0 +1,22 @@
+# This workflow will triage pull requests and apply a label based on the
+# paths that are modified in the pull request.
+#
+# To use this workflow, you will need to set up a .github/labeler.yml
+# file with configuration.  For more information, see:
+# https://github.com/actions/labeler
+
+name: Labeler
+on: [pull_request_target]
+
+jobs:
+  label:
+
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: write
+
+    steps:
+    - uses: actions/labeler@v4
+      with:
+        repo-token: "${{ secrets.GITHUB_TOKEN }}"

.github/workflows/stale.yml

@@ -0,0 +1,27 @@
+# This workflow warns and then closes issues and PRs that have had no activity for a specified amount of time.
+#
+# You can adjust the behavior by modifying this file.
+# For more information, see:
+# https://github.com/actions/stale
+name: Mark stale issues and pull requests
+
+on:
+  schedule:
+  - cron: '42 18 * * *'
+
+jobs:
+  stale:
+
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
+
+    steps:
+    - uses: actions/stale@v5
+      with:
+        repo-token: ${{ secrets.GITHUB_TOKEN }}
+        stale-issue-message: 'Stale issue message'
+        stale-pr-message: 'Stale pull request message'
+        stale-issue-label: 'no-issue-activity'
+        stale-pr-label: 'no-pr-activity'

.gitignore

@@ -0,0 +1,3 @@
+.env
+/vendor/
+index.php

CHANGELOG.md

@@ -0,0 +1,13 @@
+# Changelog
+
+### v1.0.4
+> 11-10-2024
+- Add new function pages() for Pagination.
+- Add new function filter() for filtering the data.
+- Add new function matchs() for checking duplicates data from table.
+- Updated Docs as well.
+
+### v1.0.1
+> 06-09-2024
+- Code optimize
+- add new php cURL function curl_setopt_array()

CODE_OF_CONDUCT.md

@@ -0,0 +1,36 @@
+### Code of Conduct
+
+This Code of Conduct outlines the principles and guidelines for contributing to the Supabase PHP client. By participating in this project, you agree to abide by these rules.
+
+**Respect and Inclusivity:**
+
+- Treat everyone with respect and avoid discriminatory language, harassment, or bullying.
+- Foster inclusivity by welcoming contributions from all backgrounds and perspectives.
+- Be mindful of cultural differences and respect diverse customs and beliefs.
+
+**Collaboration and Community:**
+
+- Contribute positively by sharing your knowledge, ideas, and code in a constructive manner.
+- Be open to feedback and welcome constructive criticism and suggestions.
+- Respect intellectual property and acknowledge and attribute the work of others.
+
+**Ethical Conduct:**
+
+- Use technology responsibly and avoid malicious or harmful activities.
+- Protect privacy and handle user data with care and respect.
+- Comply with laws and regulations related to open-source software and data privacy.
+
+**MIT License:**
+
+- The Supabase PHP client is licensed under the `MIT License`, allowing for modification and distribution.
+- Contributors must be acknowledged in the code or documentation.
+- The code is provided "as is" without any warranties.
+
+**Specific Guidelines:**
+
+- Write clean, well-documented, and maintainable code.
+- Ensure code quality through thorough testing.
+- Prioritize security best practices to protect against vulnerabilities.
+- Participate in discussions, answer questions, and provide support to other users.
+
+By contributing to this project, you agree to adhere to this Code of Conduct.