Age | Commit message (Collapse) | Author | |
---|---|---|---|
2020-05-26 | Add latest changes from gitlab-org/security/gitlab@12-10-stable-ee | GitLab Bot | |
2020-04-15 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-04-06 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-04-01 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-26 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-23 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-13 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-03 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-24 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-11 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-31 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-10 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-10 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-25 | Update Workhorse and Gitaly to fix a security issue | Nick Thomas | |
2019-10-11 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-02 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-25 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-01 | Update GitLab Workhorse to v8.10.0 | Nick Thomas | |
2019-08-23 | Add direct upload support for personal snippets | Jan Provaznik | |
2019-08-09 | Bump GitLab Workhorse to v8.8.0 | Stan Hu | |
This sanitizes some log messages to be consistent with CE. Full list of changes: https://gitlab.com/gitlab-org/gitlab-workhorse/blob/master/CHANGELOG | |||
2019-04-24 | Update Workhorse to v8.7.0 | Nick Thomas | |
2019-04-11 | Update GitLab Workhorse to v8.6.0 | Francisco Javier López | |
2019-04-10 | Update GitLab Workhorse to v8.5.1 | Nick Thomas | |
2019-04-04 | Renamed terminal_specification to channel_specification | Francisco 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-02 | Update gitaly and workhorse version to stable | Patrick Bajao | |
2019-04-02 | Download a folder from repository | Patrick 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-02 | Rake task for removing exif from uploads | Jan Provaznik | |
Adds a rake task which can be used for removing EXIF data from existing uploads. | |||
2019-02-13 | Update Workhorse to v8.3.1 | Nick Thomas | |
2019-02-06 | Update Workhorse to v8.3.0 | Nick Thomas | |
2019-02-04 | Update Workhorse to v8.2.0 | Nick Thomas | |
2019-01-31 | Verify that LFS upload requests are genuine | Nick 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-22 | Upgrade gitlab-workhorse to 8.1.0 | Andrew Newdigate | |
2018-12-11 | Update GitLab Workhorse to v8.0.0 | Nick Thomas | |
2018-12-11 | Upgrade to workhorse 7.6.0: | Andrew Newdigate | |
2018-12-07 | Add feature flag for workhorse content type calculation | Francisco Javier López | |
2018-12-04 | Upgrade GitLab Workhorse to v7.4.0 | Stan Hu | |
2018-12-01 | Upgrade GitLab Workhorse to v7.3.0 | Nick Thomas | |
2018-11-28 | Bump GitLab Workhorse to 7.2.1 | Stan Hu | |
https://gitlab.com/gitlab-org/gitlab-workhorse/blob/master/CHANGELOG | |||
2018-11-14 | Bump GitLab Workhorse to 7.1.1 | Stan Hu | |
This version now supports redis[s]:// URL schemes. | |||
2018-11-07 | Update GitLab-Workhorse to 7.1.0 | Andrew Newdigate | |
2018-10-02 | Update Workhorse to 7.0.0 for Gitaly's new auth scheme | Alejandro Rodríguez | |
2018-09-27 | Bump gitlab-workhorse to 6.1.1 to fix custom error handling | Stan Hu | |
2018-09-06 | Fix attachments not displaying inline with Google Cloud Storage | Stan 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-16 | Use gitlab-workhorse 6.0.0 | Jacob Vosmaer | |
2018-07-30 | Update GitLab Workhorse to v5.1.0 | Nick Thomas | |
2018-07-04 | Update Workhorse to v5.0.0 | Nick Thomas | |
2018-06-07 | Update to GitLab Workhorse v4.3.1 | Nick Thomas | |