about summary refs log tree commit diff
path: root/pkgs/development/tools/rust/cargo-make
Commit message (Collapse)AuthorAge
* cargo-make: 0.30.0 -> 0.30.1Maximilian Bosch2020-03-28
| | | | https://github.com/sagiegurari/cargo-make/releases/tag/0.30.1
* cargo-make: 0.29.0 -> 0.30.0Maximilian Bosch2020-03-23
| | | | https://github.com/sagiegurari/cargo-make/releases/tag/0.30.0
* cargo-make: 0.28.0 -> 0.29.0Maximilian Bosch2020-03-19
| | | | https://github.com/sagiegurari/cargo-make/releases/tag/0.29.0
* cargo-make: remove unnecessary attribute (#82071)Benjamin Hipple2020-03-08
| | | The default value when left unspecified is now false, so no need to state this explicitly.
* rustPlatform.fetchCargo: handle custom Cargo.lock patchfiles with validationBenjamin Hipple2020-02-28
| | | | | | | | | | Previously, we would asssert that the lockfiles are consistent during the unpackPhase, but if the pkg has a patch for the lockfile itself then we must wait until the patchPhase is complete to check. This also removes an implicity dependency on the src attribute coming from `fetchzip` / `fetchFromGitHub`, which happens to name the source directory "source". Now we glob for it, so different fetchers will work consistently.
* cargo-make: 0.27.0 -> 0.28.0Maximilian Bosch2020-02-27
| | | | https://github.com/sagiegurari/cargo-make/releases/tag/0.28.0
* treewide: change fetchCargoTarball default to opt-outBenjamin Hipple2020-02-13
| | | | | | | | | | | Changes the default fetcher in the Rust Platform to be the newer `fetchCargoTarball`, and changes every application using the current default to instead opt out. This commit does not change any hashes or cause any rebuilds. Once integrated, we will start deleting the opt-outs and recomputing hashes. See #79975 for details.
* cargo-make: 0.26.2 -> 0.27.0Maximilian Bosch2020-02-06
| | | | https://github.com/sagiegurari/cargo-make/releases/tag/0.27.0
* cargo-make: 0.26.1 -> 0.26.2Maximilian Bosch2020-01-24
| | | | https://github.com/sagiegurari/cargo-make/releases/tag/0.26.2
* cargo-make: 0.26.0 -> 0.26.1Maximilian Bosch2020-01-17
| | | | https://github.com/sagiegurari/cargo-make/releases/tag/0.26.1
* cargo-make: 0.25.1 -> 0.26.0Maximilian Bosch2020-01-10
| | | | https://github.com/sagiegurari/cargo-make/releases/tag/0.26.0
* cargo-make: 0.25.0 -> 0.25.1Maximilian Bosch2020-01-03
| | | | https://github.com/sagiegurari/cargo-make/releases/tag/0.25.1
* cargo-make: 0.24.3 -> 0.25.0Maximilian Bosch2020-01-01
| | | | https://github.com/sagiegurari/cargo-make/releases/tag/0.25.0
* cargo-make: 0.24.2 -> 0.24.3Maximilian Bosch2019-12-31
| | | | https://github.com/sagiegurari/cargo-make/releases/tag/0.24.3
* treewide: update which packages I'm currently maintainingMaximilian Bosch2019-12-26
| | | | | | | | | | | | | | | | | | Idea shamelessly stolen from 4e60b0efae56cc8e1a8a606a5a89462c38aba305. I realized that I don't really know anymore where I'm listed as maintainer and what I'm actually (co)-maintaining which means that I can't proactively take care of packages I officially maintain. As I don't have the time, energy and motivation to take care of stuff I was interested in 1 or 2 years ago (or packaged for someone else in the past), I decided that I make this explicit by removing myself from several packages and adding myself in some other stuff I'm now interested in. I've seen it several times now that people remove themselves from a package without removing the package if it's unmaintained after that which is why I figured that it's fine in my case as the affected pkgs are rather low-prio and were pretty easy to maintain.
* cargo-make: 0.24.1 -> 0.24.2Maximilian Bosch2019-12-14
| | | | https://github.com/sagiegurari/cargo-make/releases/tag/0.24.2
* cargo-make: 0.24.0 -> 0.24.1Maximilian Bosch2019-12-06
| | | | https://github.com/sagiegurari/cargo-make/releases/tag/0.24.1
* cargo-make: 0.23.0 -> 0.24.0Maximilian Bosch2019-11-22
| | | | https://github.com/sagiegurari/cargo-make/releases/tag/0.24.0
* cargo-make: 0.22.2 -> 0.23.0Maximilian Bosch2019-10-16
| | | | | | | https://github.com/sagiegurari/cargo-make/releases/tag/0.23.0 Please note that the cargo hash didn't change since no dependencies were updated (only the package version in Cargo.lock).
* cargo-make: 0.22.1 -> 0.22.2Maximilian Bosch2019-10-15
| | | | | | | https://github.com/sagiegurari/cargo-make/releases/tag/0.22.2 Also regenerated the lockfile and added it to the repo itself rather than fetching it from a GitHub gist.
* cargo-make: 0.22.0 -> 0.22.1xrelkd2019-08-21
|
* cargo-make: 0.21.0 -> 0.22.0xrelkd2019-08-15
|
* cargo-make: 0.20.0 -> 0.21.0xrelkd2019-06-27
|
* cargo-make: 0.19.5 -> 0.20.0xrelkd2019-06-16
|
* cargo-make: 0.19.4 -> 0.19.5xrelkd2019-06-10
|
* cargo-make: 0.19.3 -> 0.19.4xrelkd2019-06-01
|
* cargo-make: 0.19.2 -> 0.19.3xrelkd2019-05-28
|
* cargo-make: 0.19.1 -> 0.19.2xrelkd2019-05-27
|
* cargo-make: init at 0.19.1xrelkd2019-05-15
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-05 12:38:17 +0000