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.89.0"

[lib]
doctest = false
bench = false

[[bin]]
name = "nu_plugin_inc"
bench = false

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

semver = "1.0"
Trying this as a workaround to the [[bin]] issue 2019-12-10 03:57:55 +00:00			`[package]`
Nu glob (#4818) * Fork glob. Normalise license holder * Fix more licenses * unwraps * bad doc test 2022-03-13 18:30:27 +00:00			`authors = ["The Nushell Project Developers"]`
Add missing descriptions and licenses to subcrates 2019-12-17 17:07:00 +00: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 12:21:20 +00:00			`repository = "https://github.com/nushell/nushell/tree/main/crates/nu_plugin_inc"`
update all cargo crates to edition 2021 (#781) 2022-01-20 13:13:45 +00:00			`edition = "2021"`
renamed cargo file 2021-11-04 22:22:20 +00:00			`license = "MIT"`
			`name = "nu_plugin_inc"`
Bump version for 0.89.0 release (#11511) <!-- if this PR closes one or more issues, you can automatically link the PR with them by using one of the [linking keywords](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword), e.g. - this PR should close #xxxx - fixes #xxxx you can also mention related issues, PRs or discussions! --> - [x] reedline - [x] released - [x] pinned - [ ] git dependency check - [ ] release notes # Description <!-- Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes. Description of your pull request goes here. Provide examples and/or screenshots if your changes affect the user experience. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking 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` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass (on Windows make sure to [enable developer mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging)) - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` to run the tests for the standard library > Note > from `nushell` you can also use the `toolkit` as follows > ```bash > use toolkit.nu # or use an `env_change` hook to activate it automatically > toolkit check pr > ``` --> # 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. --> 2024-01-09 20:16:29 +00:00			`version = "0.89.0"`
Trying this as a workaround to the [[bin]] issue 2019-12-10 03:57:55 +00: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 05:17:24 +00:00			`[lib]`
			`doctest = false`
Disable auto-benchmark harness for crates (#8057) # Description This disables automatic detection of `#[bench]` and other benchmarks within the crates. Our benchmarks should all live in `benches` This fixes a problem with criterion flags and should also reduce the build requirements for `cargo bench` a bit Taken from https://github.com/nushell/nushell/pull/7952 See: https://bheisler.github.io/criterion.rs/book/faq.html#cargo-bench-gives-unrecognized-option-errors-for-valid-command-line-options # User-Facing Changes None 2023-02-12 22:22:00 +00:00			`bench = false`

			`[[bin]]`
			`name = "nu_plugin_inc"`
			`bench = false`
Trying this as a workaround to the [[bin]] issue 2019-12-10 03:57:55 +00:00
			`[dependencies]`
Bump version for 0.89.0 release (#11511) <!-- if this PR closes one or more issues, you can automatically link the PR with them by using one of the [linking keywords](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword), e.g. - this PR should close #xxxx - fixes #xxxx you can also mention related issues, PRs or discussions! --> - [x] reedline - [x] released - [x] pinned - [ ] git dependency check - [ ] release notes # Description <!-- Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes. Description of your pull request goes here. Provide examples and/or screenshots if your changes affect the user experience. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking 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` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass (on Windows make sure to [enable developer mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging)) - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` to run the tests for the standard library > Note > from `nushell` you can also use the `toolkit` as follows > ```bash > use toolkit.nu # or use an `env_change` hook to activate it automatically > toolkit check pr > ``` --> # 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. --> 2024-01-09 20:16:29 +00:00			`nu-plugin = { path = "../nu-plugin", version = "0.89.0" }`
			`nu-protocol = { path = "../nu-protocol", version = "0.89.0", features = ["plugin"] }`
renamed cargo file 2021-11-04 22:22:20 +00:00
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking 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 -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` to run the tests for the standard library > Note > from `nushell` you can also use the `toolkit` as follows > ```bash > use toolkit.nu # or use an `env_change` hook to activate it automatically > toolkit check pr > ``` --> # 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. --> 2023-05-26 15:32:48 +00:00			`semver = "1.0"`