nushell/crates/nu_plugin_inc/Cargo.toml

[package]
authors = ["The Nushell Project Developers"]
description = "A version incrementer plugin for Nushell"
repository = "https://github.com/nushell/nushell/tree/main/crates/nu_plugin_inc"
edition = "2021"
license = "MIT"
name = "nu_plugin_inc"
version = "0.72.2"

[lib]
doctest = false

[dependencies]
nu-plugin = { path="../nu-plugin", version = "0.72.2" }
nu-protocol = { path="../nu-protocol", version = "0.72.2", features = ["plugin"]}

semver = "0.11.0"
Trying this as a workaround to the [[bin]] issue 2019-12-10 04:57:55 +01:00			`[package]`
Nu glob (#4818) * Fork glob. Normalise license holder * Fix more licenses * unwraps * bad doc test 2022-03-13 19:30:27 +01:00			`authors = ["The Nushell Project Developers"]`
Add missing descriptions and licenses to subcrates 2019-12-17 18:07:00 +01:00			`description = "A version incrementer plugin for Nushell"`
Add repository info to all workspace crates (#6320) This helps people who find these crates on crates.io 2022-08-14 14:21:20 +02:00			`repository = "https://github.com/nushell/nushell/tree/main/crates/nu_plugin_inc"`
update all cargo crates to edition 2021 (#781) 2022-01-20 14:13:45 +01:00			`edition = "2021"`
renamed cargo file 2021-11-04 23:22:20 +01:00			`license = "MIT"`
			`name = "nu_plugin_inc"`
bump to dev build v0.72.2 (#7360) # Description After the 0.72.1 hotfix, let's bump our dev builds to 0.72.2. # User-Facing Changes # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. 2022-12-05 21:18:06 +01:00			`version = "0.72.2"`
Trying this as a workaround to the [[bin]] issue 2019-12-10 04:57:55 +01:00
Inc refactoring, Value helper test method extractions, and more integration helpers. (#1135) * Manifests check. Ignore doctests for now. * We continue with refactorings towards the separation of concerns between crates. `nu_plugin_inc` and `nu_plugin_str` common test helpers usage has been refactored into `nu-plugin` value test helpers. Inc also uses the new API for integration tests. 2019-12-29 06:17:24 +01:00			`[lib]`
			`doctest = false`
Trying this as a workaround to the [[bin]] issue 2019-12-10 04:57:55 +01:00
			`[dependencies]`
bump to dev build v0.72.2 (#7360) # Description After the 0.72.1 hotfix, let's bump our dev builds to 0.72.2. # User-Facing Changes # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. 2022-12-05 21:18:06 +01:00			`nu-plugin = { path="../nu-plugin", version = "0.72.2" }`
			`nu-protocol = { path="../nu-protocol", version = "0.72.2", features = ["plugin"]}`
renamed cargo file 2021-11-04 23:22:20 +01:00
			`semver = "0.11.0"`