By Ryan Blunden on September 4, 2018
Our mission is to build the best code search and browsing tool for your team to help you write the highest quality software possible.
Here’s new, what’s changed, and what’s fixed.
The browser extension used to require manual configuration when being used with a private Sourcegraph server. With the latest release, the browser extension now only needs the URL for the Sourcegraph server it’s pointing to.
This feature also shows off the new Sourcegraph settings page for the extension, which you can get to by clicking the Sourcegraph icon in the browser toolbar. More details in Sourcegraph integrations documentation.
We have simplified the process for deploying Sourcegraph to Kubernetes by eliminating Helm as a dependency, eliminating our custom monolithic config file, and eliminating Go templates in favor of using pure Kubernetes YAML. This reduces the complexity of the Sourcegraph Kubernetes deployment and makes it easier for customers to manage their own customizations.
We appreciate your patience as we have changed the Kubernetes deployment process over the last few months. The outcome is a much simpler deployment process that doesn't require external tools for deployment or YAML generation.
Existing customers can read the migration guide for more information.
By default, Sourcegraph polls code hosts to keep repository contents up to date. It uses intelligent heuristics such as average update frequency to determine the polling frequency per repository. Polling, however, falls short in cases where immediate updates are desired or when the number of repositories causes significant load on the code host. To address this, there is now a repository update webhook that lets an external service (such as a code host) trigger a repository update on Sourcegraph. The webhook is authenticated using access tokens.
See webhook docs for more information.
We're also excited to announce the alpha release of Sourcegraph extensions, a new way to enhance viewing and reviewing code in all of your favorite tools, starting with Codecov test coverage overlays on GitHub and Sourcegraph.
More Sourcegraph extensions will be released soon that overlay information (from popular 3rd-party dev tools) on GitHub, Sourcegraph, etc., related to logging, monitoring, performance, linting, profiling, security, etc. Learn more and start using Sourcegraph extensions.
Here's what the Codecov extension for Sourcegraph looks like, running on GitHub and adding test coverage overlays (as green/yellow/red line background colors):
tls-alpn-01challenges to obtain Let's Encrypt certificates. Previously Sourcegraph only supported ACME
http-01challenges, which required port 80 to be accessible.
auth.accessTokens.allowallows or restricts use of access tokens. It can be set to one of three values: "all-users-create" (the default), "none" (all access tokens are disabled), and "site-admin-create" (access tokens are enabled, but only site admins can create new access tokens). The field
auth.disableAccessTokensis now deprecated in favor of this new field.
curl -XPOST -H 'Authorization: token $ACCESS_TOKEN' $SOURCEGRAPH_ORIGIN/.api/repos/$REPO_URI/-/refresh.
Runningwhen they had been removed from Docker.
lspnetwork, leading to
dial tcp: lookup lang on 0.0.0.0:53: no such hosterrors.
Questions/feedback/complaints/requests? Contact us at [email protected], or file issues on our public issue tracker. We're planning for our next release in October right now, so the sooner we hear from you, the better!