-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Release v9.2.0 #7422
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 v9.2.0 #7422
Conversation
@@ -355,18 +355,18 @@ def test_all_languages_have_grammars | |||
scopes = YAML.load(File.read(File.expand_path("../../grammars.yml", __FILE__))).values.flatten | |||
missing = Language.all.reject { |language| language.tm_scope == "none" || scopes.include?(language.tm_scope) } | |||
message = "The following languages' scopes are not listed in grammars.yml. Please add grammars for all new languages.\n" | |||
message << "If no grammar exists for a language, mark the language with `tm_scope: none` in lib/linguist/languages.yml.\n" | |||
message += "If no grammar exists for a language, mark the language with `tm_scope: none` in lib/linguist/languages.yml.\n" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ruby 3.4 has started issuing warnings about modifying frozen strings in preparation for making this the default in Ruby 4 (See https://gist.github.com/fxn/bf4eed2505c76f4fca03ab48c43adc72 for more details.) and our tests are showing warnings like this:
/workspaces/linguist/test/test_language.rb:369: warning: literal string will be frozen in the future (run with --debug-frozen-string-literal for more information)
We don't need to enforce frozen string literals everywhere as we're only modifying strings in tests so that's all I've modified in this file.
There's a typo in the PR comment message: lanuguages vs languages. |
I've been copying and pasting this same text for several releases you're the first the notice and comment 🤣 |
This is now live everywhere, except Search, which will happen eventually - this is out of my control. |
Time for a new release 🎉
Tasks
I'm aiming to make and deploy this release by the end of the day on 5 June 2025.
NOTE: Search results will not reflect changes and new languages until the upstream internal library is updated to pull in the changes from this release and that then deployed to GitHub's Search.