« Changelog History


sourcegraph v3.27.0 Release Notes

  • ➕ Added

    • 👍 count: now supports "all" as value. Queries with count:all will return up to 999999 results. #19756
    • Credentials for Batch Changes are now validated when adding them. #19602
    • Batch Changes now ignore repositories that contain a .batchignore file. #19877 and src-cli#509
    • Side-by-side diff for commit visualization. #19553
    • 🏁 The site configuration now supports defining batch change rollout windows, which can be used to slow or disable pushing changesets at particular times of day or days of the week. #19796, #19797, and #19951.
    • Search functionality via built-in contains predicate: repo:contains(...), repo:contains.file(...), repo:contains.content(...), repo:contains.commit.after(...)`. #18584
    • 👀 Database encryption, external service config & user auth data can now be encrypted in the database using the encryption.keys config. See the docs for more info.
    • ⚡️ Repositories that gitserver fails to clone or fetch are now gradually moved to the back of the background update queue instead of remaining at the front. #20204
    • 📇 The new disableAutoCodeHostSyncs setting allows site admins to disable any periodic background syncing of configured code host connections. That includes syncing of repository metadata (i.e. not git updates, use disableAutoGitUpdates for that), permissions and batch changes changesets, but may include other data we'd sync from the code host API in the future.

    🔄 Changed

    • 📚 Bumped the minimum supported version of Postgres from 9.6 to 12. The upgrade procedure is mostly automated for existing deployments, but may require action if using the single-container deployment or an external database. See the upgrade documentation for your deployment type for detailed instructions.
    • 🔄 Changesets in batch changes will now be marked as archived instead of being detached when a new batch spec that doesn't include the changesets is applied. Once they're archived users can manually detach them in the UI. #19527
    • 0️⃣ The default replica count on sourcegraph-frontend and precise-code-intel-worker for Kubernetes has changed from 1 -> 2.
    • 🔄 Changes to code monitor trigger search queries #19680
      • A repo: filter is now required. This is due to an existing limitations where only 50 repositories can be searched at a time, so using a repo: filter makes sure the right code is being searched. Any existing code monitor without repo: in the trigger query will continue to work (with the limitation that not all repositories will be searched) but will require a repo: filter to be added when making any changes to it.
      • A patternType filter is no longer required. patternType:literal will be added to a code monitor query if not specified.
      • Added a new checklist UI to make it more intuitive to create code monitor trigger queries.
    • 🚀 Deprecated the GraphQL icon field on GenericSearchResultInterface. It will be removed in a future release. #20028
    • 🔧 Creating changesets through Batch Changes as a site-admin without configured Batch Changes credentials has been deprecated. Please configure user or global credentials before Sourcegraph 3.29 to not experience any interruptions in changeset creation. #20143
    • 🚀 Deprecated the GraphQL limitHit field on LineMatch. It will be removed in a future release. #20164

    🛠 Fixed

    • A regression caused by search onboarding tour logic to never focus input in the search bar on the homepage. Input now focuses on the homepage if the search tour isn't in effect. #19678
    • 🆕 New changes of a Perforce depot will now be reflected in master branch after the initial clone. #19718
    • 🔧 Gitolite and Other type code host connection configuration can be correctly displayed. #19976
    • 🛠 Fixed a regression that caused user and code host limits to be ignored. #20089
    • A regression where incorrect query highlighting happens for certain quoted values. #20110
    • ⚡️ We now respect the disableAutoGitUpdates setting when cloning or fetching repos on demand and during cleanup tasks that may re-clone old repos. #20194