Prepare release v1.1.1 #20
Merged
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
louis-hildebrand
force-pushed
the
release-v1.1.1
branch
5 times, most recently
from
36ba0d3
to
ae3515a
Compare
louis-hildebrand
force-pushed
the
release-v1.1.1
branch
from
ae3515a
to
5dcb368
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.
Corrupted images
Some of the images in the help page got corrupted after my last change. That seems to be because I set up the .gitattributes file to force all text files to use LF line endings. Git seems to have interpreted the PNGs as text and replaced their CRLF "line endings" with LF.
Simplified release workflow
In the current release workflow, every artifact gets zipped. The person making the release must then unzip some of them (e.g., deb, rpm, dmg). The new workflow simply uploads the deb/rpm/dmg files directly instead of zipping them.