release: v0.2.1 #830
Merged
release: v0.2.1 #830
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
EverlastingBugstopper
requested review from
lrlna and
StephenBarlow
as code owners
EverlastingBugstopper
force-pushed
the
v0.2.1
branch
4 times, most recently
from
f2f0768
to
a1bf822
Compare
EverlastingBugstopper
force-pushed
the
v0.2.1
branch
from
a1bf822
to
e52ac54
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #828
[0.2.1] - 2021-09-20
🐛 Fixes
Properly swallow unparseable git remotes - EverlastingBugstopper, issue/670 pull/760
In v0.2.0, we fixed a crash that occurred for users with non-standard git remotes. While the crash
itself no longer occurred, the crash report itself was still generated - this is no longer the case.
🛠 Maintenance
Move markdown link checker to
cargo xtask lint- EverlastingBugstopper, issue/774 pull/778We now check for broken markdown links through
xtask, meaning you can more accurately check if CI will pass locally.Migrate lints/tests from GitHub Actions to CircleCI - EverlastingBugstopper, issue/774 pull/781
Run tests on centos 7 and ensure the binary only depends on glibc <= 2.18 - EverlastingBugstopper, pull/800
Migrate release process from GitHub Actions to CircleCI - EverlastingBugstopper, issue/795 pull/808
📚 Documentation
Clarifies setting HEAD SHA for GitHub Actions - StephenBarlow, pull/763
Extended the section in the docs for configuring GitHub Actions
to include instructions for properly configuring the git context.
Fix a typo in the docs - SaintMalik, pull/762