{"owner":"influxdata","repo":"influxdb","hasSkills":true,"totalSkillsCount":2,"totalTokensCount":2947,"categories":["command-prompt","anthropic-skill"],"hasMcp":false,"mcpConfig":null,"found":[".claude/commands/back-port-enterprise-pr.md",".circleci/packages/config.yaml"],"skills":{".claude/commands/back-port-enterprise-pr.md":"---\nargument-hint: [number]\ndescription: Back-port the specified PR from the Enterprise repository.\n---\nPort changes from the `influxdb_pro` repository to this repository for the following pull request (PR): https://github.com/influxdata/influxdb_pro/pull/#$ARGUMENTS.\n\n## Approach\n\n1. Pull the latest changes on the `main` branch and start a new branch off of `main`\n2. Create a patch file using the changes in the linked PR (see the \"Patch rules\" section below)\n3. Apply the generated patch to the repository\n4. Run all tests (`cargo nextest run --workspace --no-fail-fast`) and address any test failures that arise (you may need to use `cargo insta review` if any `insta` snapshots need to be updated)\n5. Run `cargo clippy` to check lints, any fix any linter errors (you can use the `--fix` argument to `cargo clippy` to have it attempt to apply fixes manually)\n6. Run `cargo fmt --all` to format the code\n7. Commit your changes and open a PR to this repository (the commit message should be named `chore: backport <changes>` where changes are a short description of what is being back-ported from the `influxdb_pro` repository)\n8. The PR should reference the original PR on the `influxdb_pro` repository that the changes were backported from\n\n## Patch rules\n\n1. The patch should not include any files with `enterprise` in the name or file path.\n2. The patch should not include any files under the `influxdb3` directory\n3. The patch should not include any files that end in `.snap`\n4. The patch should not include changes to the `Cargo.lock` file\n",".circleci/packages/config.yaml":"# https://github.com/influxdata/ci-support/blob/main/ci-packager-next/fs/usr/bin/packager\n# uses this to calculate the version used for tarball, zip and Linux package\n# versions and git tags for this repo (https://github.com/influxdata/influxdb)\n# are used by .circleci/config.yml's 'release_filter' to determine which CI\n# jobs to run. Be default, packager will set the version to\n# 3.0.0+snapshot-<git sha> based on CIRCLE_SHA1. If CIRCLE_TAG matches one of\n# these, then packager will set the version based on the tag:\n#\n# | tag                | filename          | deb               | rpm                        |\n# |--------------------|-------------------|-------------------| -------------------------- |\n# | v3.0.0-0.alpha.1   | 3.0.0-0.alpha.1   | 3.0.0-0.alpha.1   | ver=3.0.0, rel=0.alpha.1   |\n# | v3.0.0-0.alpha.1.1 | 3.0.0-0.alpha.1.1 | 3.0.0-0.alpha.1.1 | ver=3.0.0, rel=0.alpha.1.1 |\n# | v3.0.0-0.alpha.2   | 3.0.0-0.alpha.2   | 3.0.0-0.alpha.2   | ver=3.0.0, rel=0.alpha.2   |\n# | v3.0.0-0.beta.1    | 3.0.0-0.beta.1    | 3.0.0-0.beta.1    | ver=3.0.0, rel=0.beta.1    |\n# | v3.0.0-0.beta.1.1  | 3.0.0-0.beta.1.1  | 3.0.0-0.beta.1.1  | ver=3.0.0, rel=0.beta.1.1  |\n# | v3.0.0-0.beta.2    | 3.0.0-0.beta.2    | 3.0.0-0.beta.2    | ver=3.0.0, rel=0.beta.2    |\n# | v3.0.0-0.rc.1      | 3.0.0-0.rc.1      | 3.0.0-0.rc.1      | ver=3.0.0, rel=0.rc.1      |\n# | v3.0.0             | 3.0.0             | 3.0.0-1           | ver=3.0.0, rel=1           |\n# | v3.0.0-2           | 3.0.0-2           | 3.0.0-2           | ver=3.0.0, rel=2           |\n#\n# In this manner:\n# - v3.0.0-0.alpha.1 < v3.0.0-0.alpha.1.1\n# - v3.0.0-0.alpha.1.1 < v3.0.0-0.alpha.2\n# - v3.0.0-0.alpha.2 < v3.0.0-0.beta.1\n# - v3.0.0-0.beta.1 < v3.0.0-0.beta.1.1\n# - v3.0.0-0.beta.1.1 < v3.0.0-0.beta.2\n# - v3.0.0-0.beta.2 < v3.0.0-0.rc.1\n# - v3.0.0-0.rc.1 < v3.0.0\n# - v3.0.0 < v3.0.0-2\n#\n# (use 'dpkg --compare-versions X lt Y && echo yes' for debs and\n# 'rpmdev-vercmp X Y | grep \" < \" && echo yes' for rpms)\n#\n# We use the following tag schema that supports semver as well as Linux package\n# version semantics (see https://github.com/influxdata/influxdb/pull/24751 for\n# context):\n#\n# v3.M.m[-B[.Q.q.b]]  # eg, v3.0.0, v3.0.0-2, v3.0.0-0.beta.1 or v3.0.0-0.beta.1.1\n#  | | |  |  | | |\n#  | | |  |  | |  ----------> quality release package build number\n#  | | |  |  |  ------------> quality release number\n#  | | |  |   --------------> release quality\n#  | | |   -----------------> package build number\n#  | |  --------------------> influxdb3 micro version\n#  |  ----------------------> influxdb3 minor version\n#   ------------------------> major version\n#\n# Importantly:\n# - the tag should start with 'v' (for semver tagging convention)\n# - changes in v3.M.m follow semver and indicate there are code changes\n# - '-B' should be omitted for a new v3.M.n released semver (eg, v3.0.0, not\n#   v3.0.0-1); specified starting with '2' for new package builds for this\n#   release semver (eg, v3.0.0-2, v3.0.0-3, etc); and specified with '0' for\n#   pre-release quality builds (eg, v3.0.0-0.rc.1).\n# - 'Q' is optional but when specified, 'Q' may be one of 'alpha', 'beta' or\n#   'rc'. Furthermore, when 'Q' is set:\n#   - 'B' and 'q' must also be specified with 'q' starting at '1' (eg,\n#     v3.0.0-0.alpha.1, v3.0.0-0.alpha.2, etc)\n#   - 'b' may also be specified with 'Q' and when specified, should start with\n#     '1' (eg, v3.0.0-0.alpha.1.1, v3.0.0-0.alpha.1.2, etc)\n# - changes to 'M', 'm', 'Q' and 'q' indicate influxdb code changes compared to\n#   prior tags, while 'B' and 'b' indicate only packaging changes.\n#\n# By following these rules, packager should set package versions that are\n# upgradable (eg, in package repositories).\n#\n# The CIRCLE_TAG regex enforces these rules, falling back to\n# 3.0.0+snapshot-<git hash> if it doesn't match.\nversion:\n  - match: '^v[0-9]+\\.[0-9]+\\.[0-9]+(-([2-9]|[1-9][0-9]+|0\\.(alpha|beta|rc)\\.[1-9][0-9]*(\\.[1-9][0-9]*)?))?$'\n    value: '{{env.CIRCLE_TAG[1:]}}'\n  - match: '.*'\n    value: '3.0.0+snapshot-{{env.CIRCLE_SHA1[:8]}}'\n\nsources:\n  - binary: /tmp/workspace/artifacts/influxdb3-core_x86_64-unknown-linux-gnu.tar.gz\n    target: artifacts/\n    arch:   amd64\n    plat:   linux\n\n  - binary: /tmp/workspace/artifacts/influxdb3-core_aarch64-unknown-linux-gnu.tar.gz\n    target: artifacts/\n    arch:   arm64\n    plat:   linux\n\n  - binary: /tmp/workspace/artifacts/influxdb3-core_aarch64-apple-darwin.tar.gz\n    target: artifacts/\n    arch:   arm64\n    plat:   darwin\n\n  - binary: /tmp/workspace/artifacts/influxdb3-core_x86_64-pc-windows-gnu.tar.gz\n    target: artifacts/\n    arch:   amd64\n    plat:   windows\n\npackages:\n  - name:        influxdb3-core\n    description: Monolithic time-series database\n    description_long: |\n      InfluxDB is a database built to collect, process, transform, and store\n      event and time series data. It is ideal for use cases that require\n      real-time ingest and fast query response times to build user interfaces,\n      monitoring, and automation solutions.\n    license:     MIT/Apache-2.0\n    rpm_group:   Applications/Databases\n    deb_section: database\n    vendor:      InfluxData\n    homepage:    https://influxdata.com\n    maintainer:\n      name:  support\n      email: support@influxdata.com\n    binaries:\n      # linux, darwin\n      - influxdb3\n      # windows\n      - influxdb3.exe\n    python-runtimes:\n      - source: python\n        # IMPORTANT: we intentionally use usr/lib/influxdb3 instead of\n        # usr/lib/influxdb3-{core,enterprise} to facilitate upgrades from core\n        # to enterprise and have plugins continue to work after the upgrade.\n        # This is needed since it allows us to specify the same plugin-dir\n        # (/var/lib/influxdb3/plugins) for both and the venvs will still point\n        # to a usable python in /usr/lib/influxdb3/python/...\n        target: usr/lib/influxdb3\n    extras:\n      - source: LICENSE-APACHE\n        target: usr/share/influxdb3/LICENSE-APACHE\n        doc: true\n      - source: LICENSE-MIT\n        target: usr/share/influxdb3/LICENSE-MIT\n        doc: true\n\n    perm_overrides:\n      - owner: root\n        group: root\n        perms: 0755\n        target: usr/lib/influxdb3/sysv-init.sh\n\n      - owner: root\n        group: root\n        perms: 0755\n        target: usr/lib/influxdb3/influxdb3-core-generator\n\n      - owner: root\n        group: root\n        perms: 0644\n        target: lib/systemd/system/influxdb3-core.service\n\n    source: .circleci/packages/influxdb3\n    deb:\n      conflicts:\n        - influxdb3-enterprise\n      depends:\n        - libc6  # for lintian (will pull in libgcc1 so don't need it here)\n      recommends:\n        - influxdata-archive-keyring\n    rpm:\n      # This tells rpm to do 2 things:\n      # 1. add %dir entries for each of these so that the package owns them.\n      #    Will descend to add entries for subdirectories\n      # 2. sets the rpm-attr for owner/group/perms for 'rpm -V' (owner/groups\n      #    are set in prein)\n      owned_dirs:\n        - owner: root\n          group: influxdb3\n          perms: 0755\n          target: etc/influxdb3\n        - target: usr/lib/influxdb3\n        - target: usr/share/influxdb3\n        - owner: influxdb3\n          group: influxdb3\n          perms: 0755\n          target: var/lib/influxdb3\n        - owner: influxdb3\n          group: influxdb3\n          perms: 0755\n          target: var/log/influxdb3\n      conflicts:\n        - influxdb3-enterprise\n      recommends:\n        - influxdata-archive-keyring\n"},"files":{".claude/commands/back-port-enterprise-pr.md":"---\nargument-hint: [number]\ndescription: Back-port the specified PR from the Enterprise repository.\n---\nPort changes from the `influxdb_pro` repository to this repository for the following pull request (PR): https://github.com/influxdata/influxdb_pro/pull/#$ARGUMENTS.\n\n## Approach\n\n1. Pull the latest changes on the `main` branch and start a new branch off of `main`\n2. Create a patch file using the changes in the linked PR (see the \"Patch rules\" section below)\n3. Apply the generated patch to the repository\n4. Run all tests (`cargo nextest run --workspace --no-fail-fast`) and address any test failures that arise (you may need to use `cargo insta review` if any `insta` snapshots need to be updated)\n5. Run `cargo clippy` to check lints, any fix any linter errors (you can use the `--fix` argument to `cargo clippy` to have it attempt to apply fixes manually)\n6. Run `cargo fmt --all` to format the code\n7. Commit your changes and open a PR to this repository (the commit message should be named `chore: backport <changes>` where changes are a short description of what is being back-ported from the `influxdb_pro` repository)\n8. The PR should reference the original PR on the `influxdb_pro` repository that the changes were backported from\n\n## Patch rules\n\n1. The patch should not include any files with `enterprise` in the name or file path.\n2. The patch should not include any files under the `influxdb3` directory\n3. The patch should not include any files that end in `.snap`\n4. The patch should not include changes to the `Cargo.lock` file\n",".circleci/packages/config.yaml":"# https://github.com/influxdata/ci-support/blob/main/ci-packager-next/fs/usr/bin/packager\n# uses this to calculate the version used for tarball, zip and Linux package\n# versions and git tags for this repo (https://github.com/influxdata/influxdb)\n# are used by .circleci/config.yml's 'release_filter' to determine which CI\n# jobs to run. Be default, packager will set the version to\n# 3.0.0+snapshot-<git sha> based on CIRCLE_SHA1. If CIRCLE_TAG matches one of\n# these, then packager will set the version based on the tag:\n#\n# | tag                | filename          | deb               | rpm                        |\n# |--------------------|-------------------|-------------------| -------------------------- |\n# | v3.0.0-0.alpha.1   | 3.0.0-0.alpha.1   | 3.0.0-0.alpha.1   | ver=3.0.0, rel=0.alpha.1   |\n# | v3.0.0-0.alpha.1.1 | 3.0.0-0.alpha.1.1 | 3.0.0-0.alpha.1.1 | ver=3.0.0, rel=0.alpha.1.1 |\n# | v3.0.0-0.alpha.2   | 3.0.0-0.alpha.2   | 3.0.0-0.alpha.2   | ver=3.0.0, rel=0.alpha.2   |\n# | v3.0.0-0.beta.1    | 3.0.0-0.beta.1    | 3.0.0-0.beta.1    | ver=3.0.0, rel=0.beta.1    |\n# | v3.0.0-0.beta.1.1  | 3.0.0-0.beta.1.1  | 3.0.0-0.beta.1.1  | ver=3.0.0, rel=0.beta.1.1  |\n# | v3.0.0-0.beta.2    | 3.0.0-0.beta.2    | 3.0.0-0.beta.2    | ver=3.0.0, rel=0.beta.2    |\n# | v3.0.0-0.rc.1      | 3.0.0-0.rc.1      | 3.0.0-0.rc.1      | ver=3.0.0, rel=0.rc.1      |\n# | v3.0.0             | 3.0.0             | 3.0.0-1           | ver=3.0.0, rel=1           |\n# | v3.0.0-2           | 3.0.0-2           | 3.0.0-2           | ver=3.0.0, rel=2           |\n#\n# In this manner:\n# - v3.0.0-0.alpha.1 < v3.0.0-0.alpha.1.1\n# - v3.0.0-0.alpha.1.1 < v3.0.0-0.alpha.2\n# - v3.0.0-0.alpha.2 < v3.0.0-0.beta.1\n# - v3.0.0-0.beta.1 < v3.0.0-0.beta.1.1\n# - v3.0.0-0.beta.1.1 < v3.0.0-0.beta.2\n# - v3.0.0-0.beta.2 < v3.0.0-0.rc.1\n# - v3.0.0-0.rc.1 < v3.0.0\n# - v3.0.0 < v3.0.0-2\n#\n# (use 'dpkg --compare-versions X lt Y && echo yes' for debs and\n# 'rpmdev-vercmp X Y | grep \" < \" && echo yes' for rpms)\n#\n# We use the following tag schema that supports semver as well as Linux package\n# version semantics (see https://github.com/influxdata/influxdb/pull/24751 for\n# context):\n#\n# v3.M.m[-B[.Q.q.b]]  # eg, v3.0.0, v3.0.0-2, v3.0.0-0.beta.1 or v3.0.0-0.beta.1.1\n#  | | |  |  | | |\n#  | | |  |  | |  ----------> quality release package build number\n#  | | |  |  |  ------------> quality release number\n#  | | |  |   --------------> release quality\n#  | | |   -----------------> package build number\n#  | |  --------------------> influxdb3 micro version\n#  |  ----------------------> influxdb3 minor version\n#   ------------------------> major version\n#\n# Importantly:\n# - the tag should start with 'v' (for semver tagging convention)\n# - changes in v3.M.m follow semver and indicate there are code changes\n# - '-B' should be omitted for a new v3.M.n released semver (eg, v3.0.0, not\n#   v3.0.0-1); specified starting with '2' for new package builds for this\n#   release semver (eg, v3.0.0-2, v3.0.0-3, etc); and specified with '0' for\n#   pre-release quality builds (eg, v3.0.0-0.rc.1).\n# - 'Q' is optional but when specified, 'Q' may be one of 'alpha', 'beta' or\n#   'rc'. Furthermore, when 'Q' is set:\n#   - 'B' and 'q' must also be specified with 'q' starting at '1' (eg,\n#     v3.0.0-0.alpha.1, v3.0.0-0.alpha.2, etc)\n#   - 'b' may also be specified with 'Q' and when specified, should start with\n#     '1' (eg, v3.0.0-0.alpha.1.1, v3.0.0-0.alpha.1.2, etc)\n# - changes to 'M', 'm', 'Q' and 'q' indicate influxdb code changes compared to\n#   prior tags, while 'B' and 'b' indicate only packaging changes.\n#\n# By following these rules, packager should set package versions that are\n# upgradable (eg, in package repositories).\n#\n# The CIRCLE_TAG regex enforces these rules, falling back to\n# 3.0.0+snapshot-<git hash> if it doesn't match.\nversion:\n  - match: '^v[0-9]+\\.[0-9]+\\.[0-9]+(-([2-9]|[1-9][0-9]+|0\\.(alpha|beta|rc)\\.[1-9][0-9]*(\\.[1-9][0-9]*)?))?$'\n    value: '{{env.CIRCLE_TAG[1:]}}'\n  - match: '.*'\n    value: '3.0.0+snapshot-{{env.CIRCLE_SHA1[:8]}}'\n\nsources:\n  - binary: /tmp/workspace/artifacts/influxdb3-core_x86_64-unknown-linux-gnu.tar.gz\n    target: artifacts/\n    arch:   amd64\n    plat:   linux\n\n  - binary: /tmp/workspace/artifacts/influxdb3-core_aarch64-unknown-linux-gnu.tar.gz\n    target: artifacts/\n    arch:   arm64\n    plat:   linux\n\n  - binary: /tmp/workspace/artifacts/influxdb3-core_aarch64-apple-darwin.tar.gz\n    target: artifacts/\n    arch:   arm64\n    plat:   darwin\n\n  - binary: /tmp/workspace/artifacts/influxdb3-core_x86_64-pc-windows-gnu.tar.gz\n    target: artifacts/\n    arch:   amd64\n    plat:   windows\n\npackages:\n  - name:        influxdb3-core\n    description: Monolithic time-series database\n    description_long: |\n      InfluxDB is a database built to collect, process, transform, and store\n      event and time series data. It is ideal for use cases that require\n      real-time ingest and fast query response times to build user interfaces,\n      monitoring, and automation solutions.\n    license:     MIT/Apache-2.0\n    rpm_group:   Applications/Databases\n    deb_section: database\n    vendor:      InfluxData\n    homepage:    https://influxdata.com\n    maintainer:\n      name:  support\n      email: support@influxdata.com\n    binaries:\n      # linux, darwin\n      - influxdb3\n      # windows\n      - influxdb3.exe\n    python-runtimes:\n      - source: python\n        # IMPORTANT: we intentionally use usr/lib/influxdb3 instead of\n        # usr/lib/influxdb3-{core,enterprise} to facilitate upgrades from core\n        # to enterprise and have plugins continue to work after the upgrade.\n        # This is needed since it allows us to specify the same plugin-dir\n        # (/var/lib/influxdb3/plugins) for both and the venvs will still point\n        # to a usable python in /usr/lib/influxdb3/python/...\n        target: usr/lib/influxdb3\n    extras:\n      - source: LICENSE-APACHE\n        target: usr/share/influxdb3/LICENSE-APACHE\n        doc: true\n      - source: LICENSE-MIT\n        target: usr/share/influxdb3/LICENSE-MIT\n        doc: true\n\n    perm_overrides:\n      - owner: root\n        group: root\n        perms: 0755\n        target: usr/lib/influxdb3/sysv-init.sh\n\n      - owner: root\n        group: root\n        perms: 0755\n        target: usr/lib/influxdb3/influxdb3-core-generator\n\n      - owner: root\n        group: root\n        perms: 0644\n        target: lib/systemd/system/influxdb3-core.service\n\n    source: .circleci/packages/influxdb3\n    deb:\n      conflicts:\n        - influxdb3-enterprise\n      depends:\n        - libc6  # for lintian (will pull in libgcc1 so don't need it here)\n      recommends:\n        - influxdata-archive-keyring\n    rpm:\n      # This tells rpm to do 2 things:\n      # 1. add %dir entries for each of these so that the package owns them.\n      #    Will descend to add entries for subdirectories\n      # 2. sets the rpm-attr for owner/group/perms for 'rpm -V' (owner/groups\n      #    are set in prein)\n      owned_dirs:\n        - owner: root\n          group: influxdb3\n          perms: 0755\n          target: etc/influxdb3\n        - target: usr/lib/influxdb3\n        - target: usr/share/influxdb3\n        - owner: influxdb3\n          group: influxdb3\n          perms: 0755\n          target: var/lib/influxdb3\n        - owner: influxdb3\n          group: influxdb3\n          perms: 0755\n          target: var/log/influxdb3\n      conflicts:\n        - influxdb3-enterprise\n      recommends:\n        - influxdata-archive-keyring\n"},"items":[{"name":"config.yaml","path":".circleci/packages/config.yaml","rawUrl":"https://raw.githubusercontent.com/influxdata/influxdb/HEAD/.circleci/packages/config.yaml","title":"Packages Skill","category":"anthropic-skill","format":"yaml","content":"# https://github.com/influxdata/ci-support/blob/main/ci-packager-next/fs/usr/bin/packager\n# uses this to calculate the version used for tarball, zip and Linux package\n# versions and git tags for this repo (https://github.com/influxdata/influxdb)\n# are used by .circleci/config.yml's 'release_filter' to determine which CI\n# jobs to run. Be default, packager will set the version to\n# 3.0.0+snapshot-<git sha> based on CIRCLE_SHA1. If CIRCLE_TAG matches one of\n# these, then packager will set the version based on the tag:\n#\n# | tag                | filename          | deb               | rpm                        |\n# |--------------------|-------------------|-------------------| -------------------------- |\n# | v3.0.0-0.alpha.1   | 3.0.0-0.alpha.1   | 3.0.0-0.alpha.1   | ver=3.0.0, rel=0.alpha.1   |\n# | v3.0.0-0.alpha.1.1 | 3.0.0-0.alpha.1.1 | 3.0.0-0.alpha.1.1 | ver=3.0.0, rel=0.alpha.1.1 |\n# | v3.0.0-0.alpha.2   | 3.0.0-0.alpha.2   | 3.0.0-0.alpha.2   | ver=3.0.0, rel=0.alpha.2   |\n# | v3.0.0-0.beta.1    | 3.0.0-0.beta.1    | 3.0.0-0.beta.1    | ver=3.0.0, rel=0.beta.1    |\n# | v3.0.0-0.beta.1.1  | 3.0.0-0.beta.1.1  | 3.0.0-0.beta.1.1  | ver=3.0.0, rel=0.beta.1.1  |\n# | v3.0.0-0.beta.2    | 3.0.0-0.beta.2    | 3.0.0-0.beta.2    | ver=3.0.0, rel=0.beta.2    |\n# | v3.0.0-0.rc.1      | 3.0.0-0.rc.1      | 3.0.0-0.rc.1      | ver=3.0.0, rel=0.rc.1      |\n# | v3.0.0             | 3.0.0             | 3.0.0-1           | ver=3.0.0, rel=1           |\n# | v3.0.0-2           | 3.0.0-2           | 3.0.0-2           | ver=3.0.0, rel=2           |\n#\n# In this manner:\n# - v3.0.0-0.alpha.1 < v3.0.0-0.alpha.1.1\n# - v3.0.0-0.alpha.1.1 < v3.0.0-0.alpha.2\n# - v3.0.0-0.alpha.2 < v3.0.0-0.beta.1\n# - v3.0.0-0.beta.1 < v3.0.0-0.beta.1.1\n# - v3.0.0-0.beta.1.1 < v3.0.0-0.beta.2\n# - v3.0.0-0.beta.2 < v3.0.0-0.rc.1\n# - v3.0.0-0.rc.1 < v3.0.0\n# - v3.0.0 < v3.0.0-2\n#\n# (use 'dpkg --compare-versions X lt Y && echo yes' for debs and\n# 'rpmdev-vercmp X Y | grep \" < \" && echo yes' for rpms)\n#\n# We use the following tag schema that supports semver as well as Linux package\n# version semantics (see https://github.com/influxdata/influxdb/pull/24751 for\n# context):\n#\n# v3.M.m[-B[.Q.q.b]]  # eg, v3.0.0, v3.0.0-2, v3.0.0-0.beta.1 or v3.0.0-0.beta.1.1\n#  | | |  |  | | |\n#  | | |  |  | |  ----------> quality release package build number\n#  | | |  |  |  ------------> quality release number\n#  | | |  |   --------------> release quality\n#  | | |   -----------------> package build number\n#  | |  --------------------> influxdb3 micro version\n#  |  ----------------------> influxdb3 minor version\n#   ------------------------> major version\n#\n# Importantly:\n# - the tag should start with 'v' (for semver tagging convention)\n# - changes in v3.M.m follow semver and indicate there are code changes\n# - '-B' should be omitted for a new v3.M.n released semver (eg, v3.0.0, not\n#   v3.0.0-1); specified starting with '2' for new package builds for this\n#   release semver (eg, v3.0.0-2, v3.0.0-3, etc); and specified with '0' for\n#   pre-release quality builds (eg, v3.0.0-0.rc.1).\n# - 'Q' is optional but when specified, 'Q' may be one of 'alpha', 'beta' or\n#   'rc'. Furthermore, when 'Q' is set:\n#   - 'B' and 'q' must also be specified with 'q' starting at '1' (eg,\n#     v3.0.0-0.alpha.1, v3.0.0-0.alpha.2, etc)\n#   - 'b' may also be specified with 'Q' and when specified, should start with\n#     '1' (eg, v3.0.0-0.alpha.1.1, v3.0.0-0.alpha.1.2, etc)\n# - changes to 'M', 'm', 'Q' and 'q' indicate influxdb code changes compared to\n#   prior tags, while 'B' and 'b' indicate only packaging changes.\n#\n# By following these rules, packager should set package versions that are\n# upgradable (eg, in package repositories).\n#\n# The CIRCLE_TAG regex enforces these rules, falling back to\n# 3.0.0+snapshot-<git hash> if it doesn't match.\nversion:\n  - match: '^v[0-9]+\\.[0-9]+\\.[0-9]+(-([2-9]|[1-9][0-9]+|0\\.(alpha|beta|rc)\\.[1-9][0-9]*(\\.[1-9][0-9]*)?))?$'\n    value: '{{env.CIRCLE_TAG[1:]}}'\n  - match: '.*'\n    value: '3.0.0+snapshot-{{env.CIRCLE_SHA1[:8]}}'\n\nsources:\n  - binary: /tmp/workspace/artifacts/influxdb3-core_x86_64-unknown-linux-gnu.tar.gz\n    target: artifacts/\n    arch:   amd64\n    plat:   linux\n\n  - binary: /tmp/workspace/artifacts/influxdb3-core_aarch64-unknown-linux-gnu.tar.gz\n    target: artifacts/\n    arch:   arm64\n    plat:   linux\n\n  - binary: /tmp/workspace/artifacts/influxdb3-core_aarch64-apple-darwin.tar.gz\n    target: artifacts/\n    arch:   arm64\n    plat:   darwin\n\n  - binary: /tmp/workspace/artifacts/influxdb3-core_x86_64-pc-windows-gnu.tar.gz\n    target: artifacts/\n    arch:   amd64\n    plat:   windows\n\npackages:\n  - name:        influxdb3-core\n    description: Monolithic time-series database\n    description_long: |\n      InfluxDB is a database built to collect, process, transform, and store\n      event and time series data. It is ideal for use cases that require\n      real-time ingest and fast query response times to build user interfaces,\n      monitoring, and automation solutions.\n    license:     MIT/Apache-2.0\n    rpm_group:   Applications/Databases\n    deb_section: database\n    vendor:      InfluxData\n    homepage:    https://influxdata.com\n    maintainer:\n      name:  support\n      email: support@influxdata.com\n    binaries:\n      # linux, darwin\n      - influxdb3\n      # windows\n      - influxdb3.exe\n    python-runtimes:\n      - source: python\n        # IMPORTANT: we intentionally use usr/lib/influxdb3 instead of\n        # usr/lib/influxdb3-{core,enterprise} to facilitate upgrades from core\n        # to enterprise and have plugins continue to work after the upgrade.\n        # This is needed since it allows us to specify the same plugin-dir\n        # (/var/lib/influxdb3/plugins) for both and the venvs will still point\n        # to a usable python in /usr/lib/influxdb3/python/...\n        target: usr/lib/influxdb3\n    extras:\n      - source: LICENSE-APACHE\n        target: usr/share/influxdb3/LICENSE-APACHE\n        doc: true\n      - source: LICENSE-MIT\n        target: usr/share/influxdb3/LICENSE-MIT\n        doc: true\n\n    perm_overrides:\n      - owner: root\n        group: root\n        perms: 0755\n        target: usr/lib/influxdb3/sysv-init.sh\n\n      - owner: root\n        group: root\n        perms: 0755\n        target: usr/lib/influxdb3/influxdb3-core-generator\n\n      - owner: root\n        group: root\n        perms: 0644\n        target: lib/systemd/system/influxdb3-core.service\n\n    source: .circleci/packages/influxdb3\n    deb:\n      conflicts:\n        - influxdb3-enterprise\n      depends:\n        - libc6  # for lintian (will pull in libgcc1 so don't need it here)\n      recommends:\n        - influxdata-archive-keyring\n    rpm:\n      # This tells rpm to do 2 things:\n      # 1. add %dir entries for each of these so that the package owns them.\n      #    Will descend to add entries for subdirectories\n      # 2. sets the rpm-attr for owner/group/perms for 'rpm -V' (owner/groups\n      #    are set in prein)\n      owned_dirs:\n        - owner: root\n          group: influxdb3\n          perms: 0755\n          target: etc/influxdb3\n        - target: usr/lib/influxdb3\n        - target: usr/share/influxdb3\n        - owner: influxdb3\n          group: influxdb3\n          perms: 0755\n          target: var/lib/influxdb3\n        - owner: influxdb3\n          group: influxdb3\n          perms: 0755\n          target: var/log/influxdb3\n      conflicts:\n        - influxdb3-enterprise\n      recommends:\n        - influxdata-archive-keyring\n","isInternal":false,"tokens":2569,"sizeBytes":7501},{"name":"back-port-enterprise-pr.md","path":".claude/commands/back-port-enterprise-pr.md","rawUrl":"https://raw.githubusercontent.com/influxdata/influxdb/HEAD/.claude/commands/back-port-enterprise-pr.md","title":"Command: /back-port-enterprise-pr","category":"command-prompt","format":"markdown","content":"---\nargument-hint: [number]\ndescription: Back-port the specified PR from the Enterprise repository.\n---\nPort changes from the `influxdb_pro` repository to this repository for the following pull request (PR): https://github.com/influxdata/influxdb_pro/pull/#$ARGUMENTS.\n\n## Approach\n\n1. Pull the latest changes on the `main` branch and start a new branch off of `main`\n2. Create a patch file using the changes in the linked PR (see the \"Patch rules\" section below)\n3. Apply the generated patch to the repository\n4. Run all tests (`cargo nextest run --workspace --no-fail-fast`) and address any test failures that arise (you may need to use `cargo insta review` if any `insta` snapshots need to be updated)\n5. Run `cargo clippy` to check lints, any fix any linter errors (you can use the `--fix` argument to `cargo clippy` to have it attempt to apply fixes manually)\n6. Run `cargo fmt --all` to format the code\n7. Commit your changes and open a PR to this repository (the commit message should be named `chore: backport <changes>` where changes are a short description of what is being back-ported from the `influxdb_pro` repository)\n8. The PR should reference the original PR on the `influxdb_pro` repository that the changes were backported from\n\n## Patch rules\n\n1. The patch should not include any files with `enterprise` in the name or file path.\n2. The patch should not include any files under the `influxdb3` directory\n3. The patch should not include any files that end in `.snap`\n4. The patch should not include changes to the `Cargo.lock` file\n","frontmatter":{"argument-hint":["number"],"description":"Back-port the specified PR from the Enterprise repository."},"isInternal":false,"tokens":378,"sizeBytes":1550}],"systemPromptSnippet":"<yakaai_skills repo=\"influxdata/influxdb\">\n<!-- File: .circleci/packages/config.yaml (Tokens: ~2569 | Category: anthropic-skill) -->\n# https://github.com/influxdata/ci-support/blob/main/ci-packager-next/fs/usr/bin/packager\n# uses this to calculate the version used for tarball, zip and Linux package\n# versions and git tags for this repo (https://github.com/influxdata/influxdb)\n# are used by .circleci/config.yml's 'release_filter' to determine which CI\n# jobs to run. Be default, packager will set the version to\n# 3.0.0+snapshot-<git sha> based on CIRCLE_SHA1. If CIRCLE_TAG matches one of\n# these, then packager will set the version based on the tag:\n#\n# | tag                | filename          | deb               | rpm                        |\n# |--------------------|-------------------|-------------------| -------------------------- |\n# | v3.0.0-0.alpha.1   | 3.0.0-0.alpha.1   | 3.0.0-0.alpha.1   | ver=3.0.0, rel=0.alpha.1   |\n# | v3.0.0-0.alpha.1.1 | 3.0.0-0.alpha.1.1 | 3.0.0-0.alpha.1.1 | ver=3.0.0, rel=0.alpha.1.1 |\n# | v3.0.0-0.alpha.2   | 3.0.0-0.alpha.2   | 3.0.0-0.alpha.2   | ver=3.0.0, rel=0.alpha.2   |\n# | v3.0.0-0.beta.1    | 3.0.0-0.beta.1    | 3.0.0-0.beta.1    | ver=3.0.0, rel=0.beta.1    |\n# | v3.0.0-0.beta.1.1  | 3.0.0-0.beta.1.1  | 3.0.0-0.beta.1.1  | ver=3.0.0, rel=0.beta.1.1  |\n# | v3.0.0-0.beta.2    | 3.0.0-0.beta.2    | 3.0.0-0.beta.2    | ver=3.0.0, rel=0.beta.2    |\n# | v3.0.0-0.rc.1      | 3.0.0-0.rc.1      | 3.0.0-0.rc.1      | ver=3.0.0, rel=0.rc.1      |\n# | v3.0.0             | 3.0.0             | 3.0.0-1           | ver=3.0.0, rel=1           |\n# | v3.0.0-2           | 3.0.0-2           | 3.0.0-2           | ver=3.0.0, rel=2           |\n#\n# In this manner:\n# - v3.0.0-0.alpha.1 < v3.0.0-0.alpha.1.1\n# - v3.0.0-0.alpha.1.1 < v3.0.0-0.alpha.2\n# - v3.0.0-0.alpha.2 < v3.0.0-0.beta.1\n# - v3.0.0-0.beta.1 < v3.0.0-0.beta.1.1\n# - v3.0.0-0.beta.1.1 < v3.0.0-0.beta.2\n# - v3.0.0-0.beta.2 < v3.0.0-0.rc.1\n# - v3.0.0-0.rc.1 < v3.0.0\n# - v3.0.0 < v3.0.0-2\n#\n# (use 'dpkg --compare-versions X lt Y && echo yes' for debs and\n# 'rpmdev-vercmp X Y | grep \" < \" && echo yes' for rpms)\n#\n# We use the following tag schema that supports semver as well as Linux package\n# version semantics (see https://github.com/influxdata/influxdb/pull/24751 for\n# context):\n#\n# v3.M.m[-B[.Q.q.b]]  # eg, v3.0.0, v3.0.0-2, v3.0.0-0.beta.1 or v3.0.0-0.beta.1.1\n#  | | |  |  | | |\n#  | | |  |  | |  ----------> quality release package build number\n#  | | |  |  |  ------------> quality release number\n#  | | |  |   --------------> release quality\n#  | | |   -----------------> package build number\n#  | |  --------------------> influxdb3 micro version\n#  |  ----------------------> influxdb3 minor version\n#   ------------------------> major version\n#\n# Importantly:\n# - the tag should start with 'v' (for semver tagging convention)\n# - changes in v3.M.m follow semver and indicate there are code changes\n# - '-B' should be omitted for a new v3.M.n released semver (eg, v3.0.0, not\n#   v3.0.0-1); specified starting with '2' for new package builds for this\n#   release semver (eg, v3.0.0-2, v3.0.0-3, etc); and specified with '0' for\n#   pre-release quality builds (eg, v3.0.0-0.rc.1).\n# - 'Q' is optional but when specified, 'Q' may be one of 'alpha', 'beta' or\n#   'rc'. Furthermore, when 'Q' is set:\n#   - 'B' and 'q' must also be specified with 'q' starting at '1' (eg,\n#     v3.0.0-0.alpha.1, v3.0.0-0.alpha.2, etc)\n#   - 'b' may also be specified with 'Q' and when specified, should start with\n#     '1' (eg, v3.0.0-0.alpha.1.1, v3.0.0-0.alpha.1.2, etc)\n# - changes to 'M', 'm', 'Q' and 'q' indicate influxdb code changes compared to\n#   prior tags, while 'B' and 'b' indicate only packaging changes.\n#\n# By following these rules, packager should set package versions that are\n# upgradable (eg, in package repositories).\n#\n# The CIRCLE_TAG regex enforces these rules, falling back to\n# 3.0.0+snapshot-<git hash> if it doesn't match.\nversion:\n  - match: '^v[0-9]+\\.[0-9]+\\.[0-9]+(-([2-9]|[1-9][0-9]+|0\\.(alpha|beta|rc)\\.[1-9][0-9]*(\\.[1-9][0-9]*)?))?$'\n    value: '{{env.CIRCLE_TAG[1:]}}'\n  - match: '.*'\n    value: '3.0.0+snapshot-{{env.CIRCLE_SHA1[:8]}}'\n\nsources:\n  - binary: /tmp/workspace/artifacts/influxdb3-core_x86_64-unknown-linux-gnu.tar.gz\n    target: artifacts/\n    arch:   amd64\n    plat:   linux\n\n  - binary: /tmp/workspace/artifacts/influxdb3-core_aarch64-unknown-linux-gnu.tar.gz\n    target: artifacts/\n    arch:   arm64\n    plat:   linux\n\n  - binary: /tmp/workspace/artifacts/influxdb3-core_aarch64-apple-darwin.tar.gz\n    target: artifacts/\n    arch:   arm64\n    plat:   darwin\n\n  - binary: /tmp/workspace/artifacts/influxdb3-core_x86_64-pc-windows-gnu.tar.gz\n    target: artifacts/\n    arch:   amd64\n    plat:   windows\n\npackages:\n  - name:        influxdb3-core\n    description: Monolithic time-series database\n    description_long: |\n      InfluxDB is a database built to collect, process, transform, and store\n      event and time series data. It is ideal for use cases that require\n      real-time ingest and fast query response times to build user interfaces,\n      monitoring, and automation solutions.\n    license:     MIT/Apache-2.0\n    rpm_group:   Applications/Databases\n    deb_section: database\n    vendor:      InfluxData\n    homepage:    https://influxdata.com\n    maintainer:\n      name:  support\n      email: support@influxdata.com\n    binaries:\n      # linux, darwin\n      - influxdb3\n      # windows\n      - influxdb3.exe\n    python-runtimes:\n      - source: python\n        # IMPORTANT: we intentionally use usr/lib/influxdb3 instead of\n        # usr/lib/influxdb3-{core,enterprise} to facilitate upgrades from core\n        # to enterprise and have plugins continue to work after the upgrade.\n        # This is needed since it allows us to specify the same plugin-dir\n        # (/var/lib/influxdb3/plugins) for both and the venvs will still point\n        # to a usable python in /usr/lib/influxdb3/python/...\n        target: usr/lib/influxdb3\n    extras:\n      - source: LICENSE-APACHE\n        target: usr/share/influxdb3/LICENSE-APACHE\n        doc: true\n      - source: LICENSE-MIT\n        target: usr/share/influxdb3/LICENSE-MIT\n        doc: true\n\n    perm_overrides:\n      - owner: root\n        group: root\n        perms: 0755\n        target: usr/lib/influxdb3/sysv-init.sh\n\n      - owner: root\n        group: root\n        perms: 0755\n        target: usr/lib/influxdb3/influxdb3-core-generator\n\n      - owner: root\n        group: root\n        perms: 0644\n        target: lib/systemd/system/influxdb3-core.service\n\n    source: .circleci/packages/influxdb3\n    deb:\n      conflicts:\n        - influxdb3-enterprise\n      depends:\n        - libc6  # for lintian (will pull in libgcc1 so don't need it here)\n      recommends:\n        - influxdata-archive-keyring\n    rpm:\n      # This tells rpm to do 2 things:\n      # 1. add %dir entries for each of these so that the package owns them.\n      #    Will descend to add entries for subdirectories\n      # 2. sets the rpm-attr for owner/group/perms for 'rpm -V' (owner/groups\n      #    are set in prein)\n      owned_dirs:\n        - owner: root\n          group: influxdb3\n          perms: 0755\n          target: etc/influxdb3\n        - target: usr/lib/influxdb3\n        - target: usr/share/influxdb3\n        - owner: influxdb3\n          group: influxdb3\n          perms: 0755\n          target: var/lib/influxdb3\n        - owner: influxdb3\n          group: influxdb3\n          perms: 0755\n          target: var/log/influxdb3\n      conflicts:\n        - influxdb3-enterprise\n      recommends:\n        - influxdata-archive-keyring\n\n<!-- File: .claude/commands/back-port-enterprise-pr.md (Tokens: ~378 | Category: command-prompt) -->\n---\nargument-hint: [number]\ndescription: Back-port the specified PR from the Enterprise repository.\n---\nPort changes from the `influxdb_pro` repository to this repository for the following pull request (PR): https://github.com/influxdata/influxdb_pro/pull/#$ARGUMENTS.\n\n## Approach\n\n1. Pull the latest changes on the `main` branch and start a new branch off of `main`\n2. Create a patch file using the changes in the linked PR (see the \"Patch rules\" section below)\n3. Apply the generated patch to the repository\n4. Run all tests (`cargo nextest run --workspace --no-fail-fast`) and address any test failures that arise (you may need to use `cargo insta review` if any `insta` snapshots need to be updated)\n5. Run `cargo clippy` to check lints, any fix any linter errors (you can use the `--fix` argument to `cargo clippy` to have it attempt to apply fixes manually)\n6. Run `cargo fmt --all` to format the code\n7. Commit your changes and open a PR to this repository (the commit message should be named `chore: backport <changes>` where changes are a short description of what is being back-ported from the `influxdb_pro` repository)\n8. The PR should reference the original PR on the `influxdb_pro` repository that the changes were backported from\n\n## Patch rules\n\n1. The patch should not include any files with `enterprise` in the name or file path.\n2. The patch should not include any files under the `influxdb3` directory\n3. The patch should not include any files that end in `.snap`\n4. The patch should not include changes to the `Cargo.lock` file\n</yakaai_skills>"}