Skip to content

Latest commit

 

History

History
383 lines (212 loc) · 21.5 KB

CHANGELOG.md

File metadata and controls

383 lines (212 loc) · 21.5 KB
Raw

Changelog

All notable changes to src-cli are documented in this file.

Unreleased changes

Added

Changed

Fixed

Removed

3.27.0

Added

  • Extension publishing will now add a gitHead property to the extension's manifest. #500
  • src batch [apply|preview] now ignore repositories in which a .batchignore file exists. The -force-override-ignore flag can be used to turn that behaviour off. #509
  • src search now supports streaming search. If src search is called with the flag -stream, src-cli will stream back search results as they are found. In conjunction with -stream you can also specify -display <integer> to limit the number of results that will be displayed. For example, use -display 0 if you are interested in the search statistics, such as number of results, but don't need to see the actual matches.

3.26.3

Added

  • Extension publishing will now add a gitHead property to the extension's manifest. #500
  • src batch [apply|preview] now ignore repositories in which a .batchignore file exists. The -force-override-ignore flag can be used to turn that behaviour off. #509

3.26.2

Fixed

  • Publishing of Docker images for src was broken after release 3.24.3. This has been fixed, and sourcegraph/src-cli images are available once again. #501

3.26.1

Fixed

  • Directly applying a batch change with src batch apply against Sourcegraph 3.25 or older would fail in 3.26.0. This has been fixed. #495

3.26.0

Added

  • Two new templating variables have been added: batch_change.name and batch_change.description. #491

Changed

  • Campaigns are now known as Batch Changes! The src campaign set of commands have been renamed to src batch; however, src campaign and src campaigns will be retained as aliases for src batch until the next major version of Sourcegraph. There should be no breaking changes as a result of this change. #489

3.25.3

Fixed

  • The src login command now also properly respects the -insecure-skip-verify flag.

3.25.2

Changed

  • The volume workspace Docker image is now only pulled if the volume workspace mode is in use. #477

Fixed

  • Using volume workspace mode could result in Git errors when used with Docker containers that do not run as root. These have been fixed. #478

3.25.1

Added

  • Added a flag -insecure-skip-verify to disable TLS certificate validation.

Changed

  • Deprecated cache file formats are not read by src campaign [apply|preview] anymore.

3.25.0

Added

  • src users delete now asks for confirmation to delete all users when no user ID is provided. #470

3.24.7

Fixed

  • The homebrew recipe for src-cli contained the wrong binary name.

3.24.6

Fixed

  • Workspaces could sometimes fail with docker bind mount errors, due to a race condition of multiple workspaces accessing the same auxilliary files. #468

3.24.5

Fixed

  • Importing changesets was broken in the previous release and caused a SIGSEGV error.

3.24.4

Added

  • Experimental (requires Sourcegraph 3.25 or later): workspaces in campaign specs is now available to allow users to define multiple workspaces in a single repository. #442 and #462.
  • The changesetTemplate.published field can now also be used to address a specific changeset in a repository by adding @branch-of-changeset at the end of the pattern. See #461 for an example and details.

Fixed

  • When docker becomes unresponsive src campaign [apply|preview] would get stuck and ignore Ctrl-C signals. That is now fixed.
  • The steps.files attributes in campaign specs have been broken since 3.23.2 and now work again.

3.24.3

Fixed

  • 3.24.2 disabled the faster volume workspace on macOS when one or more non-root Docker images was used by a campaign to work around the bug in issue #432. This functionality has now been restored. #434

3.24.2

Fixed

  • Executing campaigns on macOS 11 with Docker 3.1 could fail when using a volume workspace. This has been fixed. #436

3.24.1

Added

  • Internal changes to the src lsif upload command. #430

3.24.0

Added

3.23.3

Added

  • Add verbosity flag to lsif upload action. Supply -trace=1, -trace=2, or -trace=3 to the action to specify verbosity.

3.23.2

Added

  • src campaign [apply|preview] can now make use of Docker volumes, rather than bind-mounting the host filesystem. This is now the default on Intel macOS so long as the Docker images used in the campaign steps run as the same user, as volume mounts have generally better performance there. The optional -workspace flag can be used to override the default. #412

Changed

  • src login now defaults to validating against SRC_ENDPOINT if configured.

Fixed

  • src config now works correctly when provided a subject.

3.23.1

Fixed

  • The src version command didn't send any authentication headers before, which could have failed for some instance configurations. The authentication header is now properly set for the request done in this command. #411

3.23.0

Added

Changed

  • src campaign [apply|preview] now show the current execution progress in numbers next to the progress bar. #396

Fixed

  • Two race conditions in the terminal UI of src campaign [apply|preview] have been fixed. #399
  • A regression caused repositories on unsupported code host to not be skipped by src campaign [apply|preview], regardless of whether -allow-unsupported was set or not. #403
  • Previously src campaign [apply|preview] would crash when executing a campaign spec that contained steps but no changesetTemplate. #406
  • src extensions copy would copy an extension from the wrong Sourcegraph instance. #409

Removed

3.22.4

Added

  • Campaign steps may now include environment variables from outside of the campaign spec using array syntax. #392
  • A new -skip-errors flag has been added to src campaign [apply|preview] to allow users to continue execution of and upload a campaign spec even if execution failed in some repositories. #395

Fixed

  • The evaluation of the repository.branch attribute has been fixed to actually cause the correct version of the repository to be used. #393
  • Normally, when one or more repositories in a campaign generate an empty diff, a changeset spec isn't created. From src-cli 3.21.9 to 3.22.3, inclusive, re-running a campaign would result in an empty changeset spec being created by mistake if the empty changeset spec was in the execution cache, which would result in errors on Sourcegraph when applying the campaign. This has been fixed, and empty changeset specs in the cache are now treated the same way as uncached changeset specs that are empty: they are skipped, and a message is displayed in -v mode indicating the repo that was skipped. #397

3.22.3

Changed

  • src campaign [apply|preview] now prints more detailed information about the diffs produced in each repository when run in verbose mode with -v. #390
  • The dependency go-diff has been upgraded to 0.6.1 to include sourcegraph/go-diff#55.

3.22.2

Fixed

  • If src campaign [validate|apply|preview] was aborted while it was downloading repository archives it could leave behind partial ZIP files that would produce an error on the next run. This is now fixed by deleting partial files on abort. #388
  • A bug in src campaign [apply|preview] that would cause status bars in the TUI to not update has been fixed. #389

3.22.1

Fixed

  • src campaign [validate|apply|preview] now print an error and usage information if a user accidentally provides an additional argument. #384
  • Fix a regression that was introduced by #361 and caused the "Resolving repositories" step of src campaign [apply|preview] to crash when the search query in the campaign spec yielded file matches and repository matches from the same repository.

3.22.0

Fixed

  • Fixed a bug that could cause src campaign [apply|preview] to crash in rare circumstances when executing a campaign spec due to a bug in the logic for the progress bar. #378

3.21.9

Added

  • Commands for campaigns no longer require the -namespace parameter. If omitted, campaigns will use the currently authenticated user as the namespace. #372
  • src campaign [apply|preview] now caches the result of running steps in a repository even if they didn't produce changes.

3.21.8

Fixed

  • src campaign [apply|preview] could fail to parse the produced diff in a repository when git was configured to use a custom diff program. The fix is to ignore any local git configuration when running git commands. #373

3.21.7

Fixed

  • Restored backward compatibility when creating campaigns against Sourcegraph 3.19, provided author details are not provided in the campaign spec. #370

3.21.6

Fixed

  • Campaign steps run in a container that does not run as root could fail on systems that do not map the running user ID to the container, most notably desktop Linux. This has been fixed: temporary files and workspaces mounted into the container now have sufficient permissions to allow the container user to execute the step. #366
  • Executing campaigns on Windows would fail due to obscure --cidfile errors: namely, the temporary cidfile would not be removed before docker run was invoked. This has been fixed. #368
  • Unresponsive containers started by src campaign [apply|preview] can now be killed by hitting Ctrl-C. Previously the signal wasn't properly forwarded to the process in the container. #369

3.21.5

Added

  • EXPERIMENTAL: Templated campaign specs and file mounting. The campaign specs evaluated by src campaign [preview|apply] can now include template variables in steps.run, steps.env, and the new steps.files property, which allows users to create files inside the container in which the step is executed. The feature is marked as EXPERIMENTAL because it might change in the near future until we deem it non-experimental. See #361 for details.

3.21.4

Fixed

  • The src lsif upload command now respects SRC_HEADER_ environment variables for multipart uploads. These environment variables are described here. #360

3.21.3

Changed

  • The progress bar in src campaign [preview|apply] now shows when executing a step failed in a repository by styling the line red and displaying standard error output. #355
  • The src lsif upload command will give more informative output when an unexpected payload (non-JSON or non-unmarshallable) is received from the target endpoint. #359

3.21.2

Fixed

  • The cache dir used by src campaign [preview|apply] is now created before trying to create files in it, fixing a bug where the first run of the command could fail with a "file doesn't exist" error message. #352

3.21.1

Added

  • The published flag in campaign specs may now be an array, which allows only specific changesets within a campaign to be published based on the repository name. #294
  • A new src campaign new command creates a campaign spec YAML file with common values prefilled to make it easier to create a new campaign. #339
  • New experimental command src validate validates a Sourcegraph installation. #200

Changed

  • Error reporting by src campaign [preview|apply] has been improved and now includes more information about which step failed in which repository. #325
  • The default behaviour of src campaigns [preview|apply] has been changed to retain downloaded archives of repositories for better performance across re-runs of the command. To use the old behaviour and delete the archives use the -clean-archives flag. Repository archives are also not stored in the directory for temp data (see -tmp flag) anymore but in the cache directory, which can be configured with the -cache flag. To manually delete archives between runs, delete the *.zip files in the -cache directory (see src campaigns -help for its default location).
  • src campaign [preview|apply] now check whether git and docker are available before trying to execute a campaign spec's steps. #326
  • The progress bar displayed by src campaign [preview|apply] has been extended by status bars that show which steps are currently being executed for each repository. #338
  • src campaign [preview|apply] now shows a warning when no changeset specs have been created.
  • Requests sent to Sourcegraph by the src campaign commands now use gzip compression for the body when talking to Sourcegraph 3.21.0 and later. #336 and #343

Fixed

  • Log files created by src campaigns [preview|apply] are deleted again after successful execution. This was a regression and is not new behaviour. If steps failed to execute or the -keep-logs flag is set the log files are not cleaned up.
  • src campaign [preview|apply] now correctly handle the interrupt signal (emitted in a terminal with Ctrl-C) and abort execution of campaign steps, cleaning up running Docker containers.

3.21.0

Added

  • The new src login subcommand helps you authenticate src to access your Sourcegraph instance with your user credentials. #317

3.20.0

Added

  • Campaigns specs now include an optional author property. (If not included, src campaigns generates default values for author name and email.) src campaigns now includes the name and email in all changeset specs that it generates.
  • The campaigns temp directory can now be overwritten by using the -tmp flag with src campaigns [apply|preview] or by setting SRC_CAMPAIGNS_TMP_DIR. The directory is used to, for example, store log files and unzipped repository archives when executing campaign specs.

Changed

  • Repositories without a default branch are skipped when applying/previewing a campaign spec. #312
  • Log files produced when applying/previewing a campaign spec now have the .log file extension for easier opening. #315
  • Campaign specs that apply to unsupported repositories will no longer generate an error. Instead, those repositories will be skipped by default and the campaign will be applied to the supported repositories only. #314

Fixed

  • Empty changeset specs without a diff are no longer uploaded as part of a campaign spec. #313

3.19.0

Changed

  • The default branch for the src-cli project has been changed to main. #262

Fixed

  • src campaigns output has been improved in the Windows console. #274
  • src campaigns will no longer generate warnings if user.name or user.email have not been set in the global Git configuration. #277

3.18.0

Added

  • Add -dump-requests as an option to all commands that interact with the Sourcegraph API. #266

Changed

3.17.1

Added

  • Add -upload-route to the lsif upload command.

3.17.0

Added

  • New command src serve-git which can serve local repositories for Sourcegraph to clone. This was previously in a command called src-expose. See serving local repositories in our documentation to find out more. #12363
  • When used with Sourcegraph 3.18 or later, campaigns can now be created on GitLab. #231

3.16.1

Fixed

  • Fix inferred root for lsif upload command. #248

Removed

  • Removed clone-in-progress flag. #246

3.16

Added

  • Add --no-progress flag to the lsif upload command to disable verbose output in non-TTY environments.
  • SRC_HEADER_AUTHORIZATION="Bearer $(...)" is now supported for authenticating src with custom auth proxies. See auth proxy configuration docs for more information. #239
  • Pull missing docker images automatically. #191
  • Searches that result in errors will now display any alerts returned by Sourcegraph, including suggestions for how the search could be corrected. #221

Changed

  • The terminal UI has been replaced by the logger-based UI that was previously only visible in verbose-mode (-v). #228
  • Deprecated the -endpoint flag. Instead, use the SRC_ENDPOINT environment variable. #235