docs.rs failed to build hamelin_datafusion-0.3.10
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.

Visit the last successful build: hamelin_datafusion-0.7.8

Hamelin

A pipe-based query language for security event analytics.

Installation

[dependencies]
hamelin = "0.3"

Features

trino - Trino backend support

Documentation

Adding a New Crate

When adding a new publishable crate to the workspace:

Add required metadata to the crate's Cargo.toml:

[package]
name = "hamelin_newcrate"
description = "Description of the crate"
version.workspace = true
edition.workspace = true
readme.workspace = true
repository.workspace = true
homepage.workspace = true
documentation.workspace = true
license-file.workspace = true

Publish an initial version below the current workspace version. For example, if the workspace is at 0.3.9, publish 0.3.8:

# Temporarily set version to 0.3.8 in root Cargo.toml, then:
cargo publish -p hamelin_newcrate --allow-dirty
# Revert the version change after publishing

Configure trusted publishing on crates.io:
- Go to the crate's settings page on crates.io
- Click "Add" under Trusted Publishing
- Configure with:
  - Repository: perpetualsystems/hamelin
  - Workflow: hamelin-release.yaml
  - Environment: release
- Enable "Require trusted publishing for all new versions"
Add to workspace in root Cargo.toml:
- Add to members list
- Add to [workspace.dependencies] with the current workspace version

The CI will verify that all publishable crates exist on crates.io before allowing PRs to merge.

Releasing a New Version

To cut a new release of Hamelin: