[en] This release requires:

[en] Released 28 April 2023

[en] This version fixes a bug in parallel processing that could cause both the baseline and webhook workers to stop processing.

[en] Released 20 March 2023

[en] This small service release fixes a bug that caused the baseline to enter an infinite loop.

[en] Released 6 March 2023

[en] Small release for maintenance and code refactoring.

[en] Released 16 February 2023

[en] This is an important release with two new features that reduce errors in checks and in configuring files. We also updated our libraries to resolve a couple of high CVEs.

{    "//comment001": "A comment",
        ":foo0": [{"//comment0001": "A comment inside an array"},
                "foo"],
        ":foo1": {
                "//comment001": "Yet another comment",
                ":foo2": "foo2"
        }
}

[en] This release requires the following:

[en] We have dropped support for the following:

[en] The GitHub and the Azure DevOps Git integrations now have a common source code base. They’ll now be available as two different git service providers under one integration, the newly released Git Hosting 4.0 integration. Upon installing the integration, you can configure which integration you want installed.

[en] The configuration option :secret is now called :gh-secret. Please change your main config file accordingly.

[en] Most configuration options are now supported for Azure DevOps Git pull request processing. See the end of the release notes for more details.

[en] Because of significant improvements of the GitHub cloud system (the git service itself), we’ve been able to drastically decrease the event queue delay from 10 to 0.1 seconds! In practice, it means that the comments and status are now posted to the git hosting service (GitHub or Azure DevOps) up to 10 seconds faster.

[en] The environment variable ACROLINX_LOGGING_TARGET that was used to redirect the log output to the standard output has been removed due to a change in the logback library.

[en] We recommend the following approach:

[en] Inside the JAR, the file logback-stdout.xml can be used to redirect the log output. It is on the classpath and can be used as follows:

java -Dlogback.configurationFile=logback-stdout.xml -jar JARFILE ...

[en] This will redirect the log output to standard output.

[en] The user interface of the Git Hosting integration has been removed. The main reason is that all the information provided via the former user interface is now available via command line options and the log system. This means that we can spend more time on new features, rather than maintaining an old, unused one!

[en] With Azure DevOps 1.1, the persistent session ID returned by the Azure DevOps system was printed in some log entries. This has been fixed at the level of the exception system (HTTP headers aren't anymore printed to the log output in those exceptional cases).

[en] A bug has been fixed for the configuration option :allowed-filename-matches . Previously when the value of this configuration option was a string (not a vector of strings), the integration wouldn’t check any files. The configuration option now works as designed.

[en] Current differences between GitHub and Azure DevOps support:

[en] Acrolinx for Git Hosting version 3.6.0 requires the following:

[en] In the past, you could send pull requests to the Acrolinx Platform in parallel, but they were processed sequentially. This meant that the average number of files in each pull request affected the processing time. We've improved this!

[en] Acrolinx now processes incoming pull requests as quickly as possible and in parallel. With this improvement, the Acrolinx can make full use of all active language servers. Acrolinx will send as many files to the Acrolinx Platform as possible, but no more than what you configure for :acrolinx-parallel-workers. Read more about this in Configurations.

[en] You can now send the JAR log output to the standard output. To do this, set the environment variable ACROLINX_LOGGING_TARGET to the value stdout. Learn more in our article Logging and Monitoring.

[en] We found a couple of vulnerabilities in the third-party libraries that we use. That's why we've updated the library to a version where the vulnerabilities no longer exist. Time to do your part – go ahead and update your Acrolinx integration!

[en] For more details, see the National Vulnerability Database.