Sourcegraph is the standard developer platform for code search and navigation at many of the largest and most advanced technology companies. With Sourcegraph, every company has access to the same kind of tools that Google and Facebook developers use every day.
Every detail that changed in this release
🎖️ Thank you
Sourcegraph couldn't be what it is without the community.
Autocomplete suggestions make it easier to use filters in your Sourcegraph searches. Use
ctrl-space to trigger suggestions for filters you can apply to your query. As you type, the suggestions become more relevant, helping you to apply correct filter options or autocomplete repository or file names.
Sourcegraph users use the Sourcegraph browser extension to take advantage of go-to-definition and find references on their code hosts. GitLab recognizes the value this brings to developer productivity and has partnered with Sourcegraph to provide this functionality natively to all GitLab users. Read our feature announcement and GitLab’s post about collaborating in the open.
Soon, GitLab.com users will be able to opt-in to native code intelligence for public repositories by enabling Sourcegraph in their user preferences. This feature is being rolled out incrementally to public projects on GitLab.com, and will first be available on the GitLab repository.
Users with private GitLab instances or repositories can enable Sourcegraph code intelligence as of GitLab 12.5. Take a look at the Sourcegraph integration documentation for how to configure it on your instance.
Sourcegraph now supports creating and tracking code-aware search and replace campaigns on GitHub and Bitbucket Server. When running a search and replace campaign, you can preview the changes across repositories and then generate the corresponding pull requests on your GitHub and Bitbucket Server instances. Once created, you can track the PRs to completion in a burndown chart.
Sourcegraph is introducing Comby syntax for automated search and replace campaigns. Comby syntax is code-aware and simplifies finding patterns in code. This new capability makes operations that could require complex or awkward regexp queries much simpler to write.
For example, to change how errors are logged throughout your code, like in this commit in the Go source:
// match: errors.New(fmt.Sprintf(:[args])) // replace: fmt.Errorf(:[args])
With the completion of the Java LSIF indexer, LSIF-based precise code intelligence now supports five languages: Go, Typescript, Java, C++, and Python. See lsif.dev for the most up-to-date information on the list of languages with LSIF indexers.
We are looking for feedback from project owners interested in trying out precise code intelligence! Use our new LSIF quickstart guide to try it out manually before adding it as a step in your CI.
Customers wanting better indexed search performance or wishing to add many more thousands of repositories to Sourcegraph are now in luck! Sourcegraph's indexed search can now scale horizontally in cluster deployments.
The Kubernetes deployment manifest for indexed-search services has changed from a Normal Service to a Headless Service. This enables Sourcegraph to individually resolve indexed-search pods. Services are immutable, so a migration is required.
IMPORTANT: required migration for all Kubernetes deployments. Please see the 3.10 migration guide for details.
As part of Sourcegraph’s ongoing commitment to providing the highest quality, stable releases, our manual QA process has in the last two months been turned into a fully automated regression testing suite. We continue to aggressively invest in automated testing of Sourcegraph to provide extremely stable and reliable releases, and ultimately better features for our users. Look forward to reading more about this in an upcoming blogpost from Sourcegraph CTO, Beyang Liu, on our blog.
replicafield of the
indexed-searchStatefulSet. See configure indexed-search replica count. #5725
excludeconfig option. #6035
sourcegraph/serverDocker deployments now support the environment variable
IGNORE_PROCESS_DEATH. If set to true the container will keep running, even if a subprocess has died. This is useful when manually fixing problems in the container which the container refuses to start. For example a bad database migration.
Stringin our GraphQL API that contain JSONC now have the custom scalar type
ZOEKT_HOSTenvironment variable has been deprecated. Please use
ZOEKT_HOSTwill be removed in 3.12.
redis-check-aof --fixon startup to fix corrupted AOF files. #651
PageInfoobject now returns a
Stringinstead of an
endCursor, and likewise for the
aftersearch field. Experimental paginated search API users may need to update their usages to replace
IDcursor types with
type:pathsearch queries now correctly work in indexed search again. #6220
The changelog for this and previous releases is available on GitHub.
Thank you to the many people who contributed to Sourcegraph since the last release!
From the entire @sourcegraph team, happy coding!