Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release v7.9.0 #4816

Merged
merged 9 commits into from
Mar 19, 2020
Merged

Release v7.9.0 #4816

merged 9 commits into from
Mar 19, 2020

Conversation

lildude
Copy link
Member

@lildude lildude commented Mar 10, 2020

Description

Just over a month since the last release so time for another.

  • Test deploy to GitHub.com locally and in staging
  • Deploy to GitHub.com
  • Deploy grammar update to syntax highlighter
  • 🎉

/cc @rewinfrey

[ Template removed as it doesn't apply ]

rewinfrey and others added 4 commits March 9, 2020 16:18
We need this to ensure the versioning used during testing on GitHub.com doesn't cause caching problems in future
@lildude
Copy link
Member Author

lildude commented Mar 11, 2020

I'm going to use this opportunity to test the changes in #4730 too.

/cc @smola

Some files failed with "invalid byte sequence in UTF-8 (ArgumentError)"
when BlobHelper#lines was called. Some problematic files include
UTF-16LE samples such as test/fixtures/Data/utf16le.

Errors were not present when computing stats from git repositories,
since git blobs are always read as ASCII-8BIT and that was working
correctly. However, when using FileBlob, encoding could be ASCII-8BIT,
UTF-8 or other, depending on the runtime value of Encoding.external_encoding.

Tests were not catching the error since they were forcing
Encoding.external_encoding to be ASCII-8BIT (introduced in #1211). So the
error would only be seen in wild usage (see issue #353).

This commit forces ASCII-8BIT on File.read calls. The error is still
present if using memory blobs with other encodings.
@Alhadis Alhadis mentioned this pull request Mar 16, 2020
3 tasks
@lildude lildude marked this pull request as ready for review March 19, 2020 11:46
@lildude lildude merged commit 40992ba into master Mar 19, 2020
@lildude lildude deleted the release-v7.9.0 branch March 19, 2020 15:09
@lildude
Copy link
Member Author

lildude commented Mar 19, 2020

Linguist v7.9.0 is now live on GitHub.com.

@mahrud
Copy link
Contributor

mahrud commented Jun 10, 2020

Do you have an estimate for when the next release would be? (Sorry for unearthing this thread!)

@lildude
Copy link
Member Author

lildude commented Jun 10, 2020

@mahrud In the next week or two. I've already started the process so it's mostly testing and deploy queuing to do. I'll be opening the PRs etc today.

@github-linguist github-linguist locked as resolved and limited conversation to collaborators Jun 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants