Skip to content

Releases: augentic/.github

Release v0.2.0

Choose a tag to compare

@github-actions github-actions released this 28 Sep 21:52
Immutable release. Only release title and notes can be modified.
a706c0e

Added

  • ci.yaml: new wasm-packages input (space-separated workspace members,
    default empty = whole workspace) narrowing which packages the per-target
    clippy passes lint. Workspaces that mix host-only crates with guest
    components can now pass targets: wasm32-wasip2 at all.
  • mise/rust.toml: lint-host and lint-wasm (the two halves of lint),
    fmt-check, vet-regen and a cov coverage helper
    (cargo llvm-cov nextest --workspace --all-features --summary-only).
  • mise/rust.toml: consumer knobs read from [env]: WASM32_PACKAGES
    (mirrors wasm-packages) and OUTDATED_IGNORE (comma-separated, mirrors
    audit.yaml's outdated input).
  • README: consumer configuration, the wasm32 lint convention and a table
    mapping each ci.yaml job to its mise/rust.toml task.

Changed

  • ci.yaml and mise/rust.toml (lint-wasm): the per-target clippy pass
    builds --lib --bins --examples instead of --all-targets, and the
    per-target cargo hack clippy --each-feature pass uses cargo's default
    targets (lib + bins). Integration tests and benches, whose dev-dependencies
    are host-only in most workspaces, are no longer compiled for wasm32.
    Convention: any bin or example in the wasm32 scope that is host-only must be
    cfg-gated to an empty main on wasm32.
  • mise/rust.toml: vet is now check-only (cargo vet --locked), matching
    the CI vet job; the three regenerate steps moved to vet-regen.
  • mise/rust.toml: ci runs exactly the CI jobs
    (fmt-check, lint, test, test-docs, docs, vet, deny).
    outdated and deps remain in check; fmt no longer rewrites sources
    as part of ci.
  • mise/rust.toml: outdated no longer hard-codes omnia's ignore list; set
    OUTDATED_IGNORE instead.
  • mise/rust.toml: lint passes --locked; RUSTFLAGS=-Dwarnings is set
    on lint, test, test-docs and docs, and docs also sets
    RUSTDOCFLAGS=-Dwarnings, so mise run ci matches the workflow's global
    environment.

What's Changed

Full Changelog: v0.1.2...v0.2.0

Release v0.1.2

Choose a tag to compare

@github-actions github-actions released this 28 Sep 02:07
Immutable release. Only release title and notes can be modified.
36919fc

Changed

  • ci.yaml: the test job runs cargo nextest run --workspace --all-features
    once instead of cargo hack nextest run --each-feature. The per-feature
    matrix rebuilt heavy dependencies for every crate/feature pair and ran the
    slow integration tests serially, roughly doubling the job while executing
    exactly the same set of tests; feature-gated tests in the consuming
    repositories are all positively gated, so --all-features is a superset.
    Per-feature compile coverage remains in the clippy job.
  • mise/rust.toml: the test task makes the same change so it keeps
    mirroring CI, and no longer depends on cargo-hack.

What's Changed

Full Changelog: v0.1.1...v0.1.2

Release v0.1.1

Choose a tag to compare

@github-actions github-actions released this 28 Sep 00:57
Immutable release. Only release title and notes can be modified.
5604e3f

Changed

  • ci.yaml: the test job no longer passes --tests to cargo hack nextest run,
    which was building every test target per feature combination causing excessive
    run time for little benefit.

What's Changed

Full Changelog: v0.1.0...v0.1.1

Release v0.1.0

Choose a tag to compare

@github-actions github-actions released this 27 Sep 23:22
Immutable release. Only release title and notes can be modified.
badae84

Added

  • Reusable Rust workflows: ci.yaml, audit.yaml, release.yaml,
    patch.yaml, publish.yaml, crates.yaml, wasm.yaml.
  • Composite actions: git-identity, cargo-version, release-notes.
  • Shared mise tasks for Rust workspaces (mise/rust.toml).
  • lint.yaml running actionlint over this repository's workflows.
  • Tagged releases of this repository via the Release workflow.
  • release.yaml, publish.yaml and patch.yaml resolve their composite
    actions at the same commit as the workflow, so pinning a tag pins the
    actions too.

What's Changed

New Contributors

Full Changelog: https://github.com/augentic/.github/commits/v0.1.0