Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/GITLAB_WORKHORSE_VERSION
AgeCommit message (Collapse)Author
2019-04-24Update Workhorse to v8.7.0Nick Thomas
2019-04-11Update GitLab Workhorse to v8.6.0Francisco Javier López
2019-04-10Update GitLab Workhorse to v8.5.1Nick Thomas
2019-04-04Renamed terminal_specification to channel_specificationFrancisco Javier López
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.
2019-04-02Update gitaly and workhorse version to stablePatrick Bajao
2019-04-02Download a folder from repositoryPatrick Bajao
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.
2019-04-02Rake task for removing exif from uploadsJan Provaznik
Adds a rake task which can be used for removing EXIF data from existing uploads.
2019-02-13Update Workhorse to v8.3.1Nick Thomas
2019-02-06Update Workhorse to v8.3.0Nick Thomas
2019-02-04Update Workhorse to v8.2.0Nick Thomas
2019-01-31Verify that LFS upload requests are genuineNick Thomas
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.
2019-01-22Upgrade gitlab-workhorse to 8.1.0Andrew Newdigate
2018-12-11Update GitLab Workhorse to v8.0.0Nick Thomas
2018-12-11Upgrade to workhorse 7.6.0:Andrew Newdigate
2018-12-07Add feature flag for workhorse content type calculationFrancisco Javier López
2018-12-04Upgrade GitLab Workhorse to v7.4.0Stan Hu
2018-12-01Upgrade GitLab Workhorse to v7.3.0Nick Thomas
2018-11-28Bump GitLab Workhorse to 7.2.1Stan Hu
https://gitlab.com/gitlab-org/gitlab-workhorse/blob/master/CHANGELOG
2018-11-14Bump GitLab Workhorse to 7.1.1Stan Hu
This version now supports redis[s]:// URL schemes.
2018-11-07Update GitLab-Workhorse to 7.1.0Andrew Newdigate
2018-10-02Update Workhorse to 7.0.0 for Gitaly's new auth schemeAlejandro Rodríguez
2018-09-27Bump gitlab-workhorse to 6.1.1 to fix custom error handlingStan Hu
2018-09-06Fix attachments not displaying inline with Google Cloud StorageStan Hu
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
2018-08-16Use gitlab-workhorse 6.0.0Jacob Vosmaer
2018-07-30Update GitLab Workhorse to v5.1.0Nick Thomas
2018-07-04Update Workhorse to v5.0.0Nick Thomas
2018-06-07Update to GitLab Workhorse v4.3.1Nick Thomas
2018-06-01Update to GitLab Workhorse v4.3.0Nick Thomas
2018-05-22Upgrade workhorse to v4.2.1Alessio Caiazza
2018-05-01Use gitlab-workhorse 4.2.0Jacob Vosmaer
2018-04-12Update GitLab Workhorse to v4.1.0Nick Thomas
2018-03-07Upgrade Workhorse to 4.0.0Kamil Trzciński
2018-03-02Upgrade GitLab Workhorse to 3.8.0 for structured logging supportAndrew Newdigate
2018-02-06Upgrade GitLab Workhorse to v3.6.0Kamil Trzciński
2018-01-22Use gitlab-workhorse 3.5.1Jacob Vosmaer
2018-01-09Add option to disable git archive caching in workhorseJacob Vosmaer
2018-01-08Use workhorse 3.4.0Jacob Vosmaer
2017-11-14Update gitlab-workhorse to v3.3.1Nick Thomas
2017-10-30Support show-all-refs for git over HTTPNick Thomas
2017-10-05Update required Workhorse version to v3.2.0Alejandro Rodríguez
2017-09-20Use gitlab-workhorse 3.1.0Jacob Vosmaer
2017-07-11Migrate Workhorse SendBlob to GitalyAhmad Sherif
2017-07-06Upgrade GitLab Workhorse to v2.3.0Nick Thomas
2017-06-22Use gitlab-workhorse 2.2.0Jacob Vosmaer
2017-06-09Update gitlab-workhorse to v2.1.1Nick Thomas
2017-05-03Use gitlab-workhorse 2.0.0Jacob Vosmaer
2017-04-05Use gitlab-workhorse 1.4.3Jacob Vosmaer
2017-03-24Use gitlab-workhorse 1.4.2Jacob Vosmaer
Fixes silent failure of `git clone` when Gitaly is not running.
2017-03-13Use gitlab-workhorse 1.4.1Jacob Vosmaer
2017-03-06Use gitlab-workhorse 1.4.0Jacob Vosmaer
Bug fixes, Gitaly gRPC support, experimental Redis integration.
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-28 04:07:33 +0300