summaryrefslogtreecommitdiff
path: root/GITLAB_WORKHORSE_VERSION
Commit message (Collapse)AuthorAgeFilesLines
* Update Workhorse to v8.7.0Nick Thomas2019-04-241-1/+1
|
* Update GitLab Workhorse to v8.6.0Francisco Javier López2019-04-111-1/+1
|
* Update GitLab Workhorse to v8.5.1Nick Thomas2019-04-101-1/+1
|
* Renamed terminal_specification to channel_specificationFrancisco Javier López2019-04-041-1/+1
| | | | | | We're moving from using terminology related to terminals when we refer to Websockets connections in Workhorse. It's more appropiate a concept like channel.
* Update gitaly and workhorse version to stablePatrick Bajao2019-04-021-1/+1
|
* Download a folder from repositoryPatrick Bajao2019-04-021-1/+1
| | | | | | | | Add `GetArchiveRequest` to git-archive params. Modifies `Git::Repository#archive_metadata` to append `path` to `ArchivePrefix` so it'll not hit the cache of repository archive when it already exists.
* Rake task for removing exif from uploadsJan Provaznik2019-04-021-1/+1
| | | | | Adds a rake task which can be used for removing EXIF data from existing uploads.
* Update Workhorse to v8.3.1Nick Thomas2019-02-131-1/+1
|
* Update Workhorse to v8.3.0Nick Thomas2019-02-061-1/+1
|
* Update Workhorse to v8.2.0Nick Thomas2019-02-041-1/+1
|
* Verify that LFS upload requests are genuineNick Thomas2019-01-311-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | LFS uploads are handled in concert by workhorse and rails. In normal use, workhorse: * Authorizes the request with rails (upload_authorize) * Handles the upload of the file to a tempfile - disk or object storage * Validates the file size and contents * Hands off to rails to complete the upload (upload_finalize) In `upload_finalize`, the LFS object is linked to the project. As LFS objects are deduplicated across all projects, it may already exist. If not, the temporary file is copied to the correct place, and will be used by all future LFS objects with the same OID. Workhorse uses the Content-Type of the request to decide to follow this routine, as the URLs are ambiguous. If the Content-Type is anything but "application/octet-stream", the request is proxied directly to rails, on the assumption that this is a normal file edit request. If it's an actual LFS request with a different content-type, however, it is routed to the Rails `upload_finalize` action, which treats it as an LFS upload just as it would a workhorse-modified request. The outcome is that users can upload LFS objects that don't match the declared size or OID. They can also create links to LFS objects they don't really own, allowing them to read the contents of files if they know just the size or OID. We can close this hole by requiring requests to `upload_finalize` to be sourced from Workhorse. The mechanism to do this already exists.
* Upgrade gitlab-workhorse to 8.1.0Andrew Newdigate2019-01-221-1/+1
|
* Update GitLab Workhorse to v8.0.0Nick Thomas2018-12-111-1/+1
|
* Upgrade to workhorse 7.6.0:Andrew Newdigate2018-12-101-1/+1
|
* Add feature flag for workhorse content type calculationFrancisco Javier López2018-12-061-1/+1
|
* Upgrade GitLab Workhorse to v7.4.0Stan Hu2018-12-041-1/+1
|
* Upgrade GitLab Workhorse to v7.3.0Nick Thomas2018-11-301-1/+1
|
* Bump GitLab Workhorse to 7.2.1Stan Hu2018-11-281-1/+1
| | | | https://gitlab.com/gitlab-org/gitlab-workhorse/blob/master/CHANGELOG
* Bump GitLab Workhorse to 7.1.1Stan Hu2018-11-141-1/+1
| | | | This version now supports redis[s]:// URL schemes.
* Update GitLab-Workhorse to 7.1.0upgrade-workhorse-7-1-0Andrew Newdigate2018-11-071-1/+1
|
* Update Workhorse to 7.0.0 for Gitaly's new auth schemeAlejandro Rodríguez2018-10-011-1/+1
|
* Bump gitlab-workhorse to 6.1.1 to fix custom error handlingStan Hu2018-09-271-1/+1
|
* Fix attachments not displaying inline with Google Cloud StorageStan Hu2018-09-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | There were several issues: 1. With Google Cloud Storage, we can't override the Content-Type with Response-Content-Type once it is set. Setting the value to `application/octet-stream` doesn't buy us anything. GCS defaults to `application/octet-stream`, and AWS uses `binary/octet-stream`. Just remove this `Content-Type` when we upload new files. 2. CarrierWave and fog-google need to support query parameters: https://github.com/fog/fog-google/pull/409/files, https://github.com/carrierwaveuploader/carrierwave/pull/2332/files. CarrierWave has been monkey-patched until an official release. 3. Workhorse also needs to remove the Content-Type header in the request (https://gitlab.com/gitlab-org/gitlab-workhorse/blob/ef80978ff89e628c8eeb66556720e30587d3deb6/internal/objectstore/object.go#L66), or we'll get a 403 error when uploading due to signed URLs not matching the headers. Upgrading to Workhorse 6.1.0 for https://gitlab.com/gitlab-org/gitlab-workhorse/merge_requests/297 will make Workhorse use the headers that are used by Rails. Closes #49957
* Use gitlab-workhorse 6.0.0workhorse-6.0.0Jacob Vosmaer2018-08-161-1/+1
|
* Update GitLab Workhorse to v5.1.0nick.thomas/gitlab-ce-workhorse-5-1-0Nick Thomas2018-07-301-1/+1
|
* Update Workhorse to v5.0.0Nick Thomas2018-07-041-1/+1
|
* Update to GitLab Workhorse v4.3.1Nick Thomas2018-06-071-1/+1
|
* Update to GitLab Workhorse v4.3.0Nick Thomas2018-06-011-1/+1
|
* Upgrade workhorse to v4.2.1Alessio Caiazza2018-05-221-1/+1
|
* Use gitlab-workhorse 4.2.0Jacob Vosmaer2018-05-011-1/+1
|
* Update GitLab Workhorse to v4.1.0Nick Thomas2018-04-121-1/+1
|
* Upgrade Workhorse to 4.0.0upgrade-workhorse-4.0.0Kamil Trzciński2018-03-071-1/+1
|
* Upgrade GitLab Workhorse to 3.8.0 for structured logging supportan/workhorse-3.8.0Andrew Newdigate2018-03-021-1/+1
|
* Upgrade GitLab Workhorse to v3.6.0Kamil Trzciński2018-02-061-1/+1
|
* Use gitlab-workhorse 3.5.1workhorse-3.5.1Jacob Vosmaer2018-01-221-1/+1
|
* Add option to disable git archive caching in workhorseoption-disable-archive-cacheJacob Vosmaer2018-01-091-1/+1
|
* Use workhorse 3.4.0workhorse-3.4.0Jacob Vosmaer2018-01-081-1/+1
|
* Update gitlab-workhorse to v3.3.1Nick Thomas2017-11-141-1/+1
|
* Support show-all-refs for git over HTTPNick Thomas2017-10-301-1/+1
|
* Update required Workhorse version to v3.2.0workhorse-updateAlejandro Rodríguez2017-10-051-1/+1
|
* Use gitlab-workhorse 3.1.0Jacob Vosmaer2017-09-201-1/+1
|
* Migrate Workhorse SendBlob to GitalyAhmad Sherif2017-07-111-1/+1
|
* Upgrade GitLab Workhorse to v2.3.0Nick Thomas2017-07-061-1/+1
|
* Use gitlab-workhorse 2.2.0Jacob Vosmaer2017-06-221-1/+1
|
* Update gitlab-workhorse to v2.1.1Nick Thomas2017-06-091-1/+1
|
* Use gitlab-workhorse 2.0.0Jacob Vosmaer2017-05-031-1/+1
|
* Use gitlab-workhorse 1.4.3Jacob Vosmaer2017-04-051-1/+1
|
* Use gitlab-workhorse 1.4.2Jacob Vosmaer2017-03-241-1/+1
| | | | Fixes silent failure of `git clone` when Gitaly is not running.
* Use gitlab-workhorse 1.4.1Jacob Vosmaer2017-03-131-1/+1
|
* Use gitlab-workhorse 1.4.0Jacob Vosmaer2017-03-061-1/+1
| | | | Bug fixes, Gitaly gRPC support, experimental Redis integration.