summaryrefslogtreecommitdiff
path: root/Cargo.lock
Commit message (Collapse)AuthorAge
* Restore rust-toolchain file.Owen Jacobson2020-06-17
| | | | | | | | | | | | | | | | | | | Removing this file broke Heroku deployments. The emk/rust buildpack relies on this file to detect the Rust version, and as this code _requires_ a nightly, the default stable version fails to deploy. Unfortunately, this effectively leaves the project pinned to a specific nightly version until and unless one of a few things happens: * We remove the test step that verifies formatting, * Travis adds a non-minimal Rust profile, * We migrate CI to a service that supports a more complete Rust profile, or * Nightly has rustfmt again. See <https://github.com/emk/heroku-buildpack-rust#specifying-which-version-of-rust-to-use>. This reverts commit f43bcb502435ccd99e163671204371dd8b62024f.
* Stop releasing semver versions.Owen Jacobson2020-06-17
| | | | That was an experiment that didn't really go anywhere. There are no meaningful "versions" of this software - it runs on a single host, and there are no compatibility promises.
* (cargo-release) start next development iteration 0.4.2-alpha.0Owen Jacobson2020-06-16
|
* (cargo-release) version 0.4.1Owen Jacobson2020-06-16
|
* (cargo-release) start next development iteration 0.4.1-alpha.0Owen Jacobson2020-06-05
|
* (cargo-release) version 0.4.0Owen Jacobson2020-06-05
|
* (cargo-release) start next development iteration 0.3.1-alpha.0Owen Jacobson2020-06-04
|
* (cargo-release) version 0.3.0Owen Jacobson2020-06-04
|
* (cargo-release) start next development iteration 0.2.1-alpha.0Owen Jacobson2020-06-04
|
* (cargo-release) version 0.2.0Owen Jacobson2020-06-04
|
* Markdown support.Owen Jacobson2020-06-04
| | | | | | | | This accomplishes two things: 1. The og cards and page title no longer contain half-baked markup. Instead, they show the markdown equivalent, which is generally pretty friendly. In other words, the page title is "Have you checked `resolv.conf`?" and not "Have you checked <code>resolve.conf</code>?" 2. Phrases can now start with terms other than "Have you checked".
* Port things-to-check to Rust as a learning exercise.Owen Jacobson2020-06-03
This is somewhat overengineered in places, but does the job and exposes broadly the same interfaces as the Python version. Builds with emk/rust.