Lines Matching refs:crate

38    have uncovered a bug in a Tracing crate, creating a new issue in the
126 example), it is either adding new functionality to a crate or it is fixing
128 include one or more tests to ensure that the crate does not regress in the future.
134 Integration tests go in the same crate as the code they are testing. Each sub
135 crate should have a `dev-dependency` on `tracing` itself. This makes all
136 `tracing` utilities available to use in tests, no matter the crate being
140 integration tests in the crate and follow the style.
249   * be prefixed with the name of the crate being changed (without the
405 When releasing a new version of a crate, follow these steps:
407 1. **Ensure that the release crate has no path dependencies.** When the HEAD
408    version of a Tracing crate requires unreleased changes in another Tracing crate,
409    the crates.io dependency on the second crate will be replaced with a path
411    publishing the dependent crate, any path dependencies must also be published.
414    1. Starting with the first path dependency in the crate to be released,
420       dependent crate to depend on the crates.io version.
421    4. When all path dependencies have been published, the dependent crate may
424    To verify that a crate is ready to publish, run:
434    attribute in the crate's `lib.rs` and the "Documentation" link in the crate's
436 4. **Update the changelog for the crate.** Each crate in the Tokio repository
437    has its own `CHANGELOG.md` in that crate's subdirectory. Any changes to that
438    crate since the last release should be added to the changelog. Change
441    Other entries in that crate's changelog may also be used for reference.
443    crate with the Git tag for the most recent release version. If there are any
450 7. **Release the crate.** Run the following command: