Blog
Our changelog, announcements, dev posts, and anything else we think you'll find interesting.
Sourcegraph 3.34 release
Sourcegraph 3.34 is now available! Here are some highlights from this release:
Troubleshoot your searches with the "no results" page
Searches that return no results can result in a confusing experience. When this occurs, we now display helpful tips on how to use search, examples of how to solve common query issues, and links to tutorial videos addressing common use cases.
Quickly navigate your Go code with Find Implementations
If you have precise code intelligence enabled for your Go repositories, you can now click on "Find Implementations" to navigate to a symbol's interface definition. If you're at the interface definition itself, clicking on the same button will show all the places where the interface is being implemented, allowing you to explore how it's being used by other users across repositories. It can also show you which interfaces a struct implements.
Changelog highlights
- SearchAdded a help page providing search tips if a search returns no results, making it easier to troubleshoot your query.
- SearchIn order to reduce load on the Gitserver service on installations with a large number of repositories, the search indexer only polls repositories that have been marked as changed. If you notice index staleness you can try disabling by setting the environment variable `SRC_SEARCH_INDEXER_EFFICIENT_POLLING_DISABLED` on `sourcegraph-frontend`.
- AdminTo help site admins debug issues with webhook delivery, we have added logging of incoming Batch Changes webhooks. By default, sites without encryption will log webhooks for three days and sites with encryption will not log webhooks.
- Batch ChangesTo allow writing to the `.github` directory in repositories, Batch Changes now requests the `workflow` scope on GitHub personal access tokens. If you have already configured a GitHub PAT for Batch Changes, we suggest adding this scope.
- SearchTo increase search speed, the search UI's repository count and the GraphQL API's `search().repositories`/`search().repositoriesCount` have changed semantics from being the set of searchable repositories to the set of repositories with matches. In a future release, we’ll introduce separate fields for searchable repositories.
- SearchVersion contexts and `repogroup` filters (deprecated in v3.33) have been removed in favor of search contexts.
- SearchSaved search notifications (deprecated in v3.31.0) have been removed in favor of code monitoring.