| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Closes #8215
|
|
|
|
| |
Closes #8215
|
|
|
|
| |
Closes #8196
|
|
|
|
| |
Closes #8158
|
|
|
|
|
|
|
|
|
| |
Since the 'CMAKE_' prefix is reserved for cmake's own private use.
Ref: https://cmake.org/cmake/help/latest/manual/cmake-variables.7.html
Reported-by: Boris Rasin
Fixes #7988
Closes #8044
|
|
|
|
|
|
|
|
| |
Previously we saw errors attempting to run "brew install", see
https://github.com/curl/curl/runs/4095721123?check_suite_focus=true for
an example, since this command is idempotent, it is safe to run again.
Closes #7955
|
|
|
|
|
|
|
| |
Unfortunately the GitHub API requires a token with write permission
for both issues and pull-requests to edit labels on even just PRs.
Follow up to #7897
|
|
|
|
|
|
|
|
|
| |
Follow up to #7897
Test references to see if permissions are now sufficient:
Closes #7832
Closes #7897
|
|
|
|
|
|
|
|
|
|
|
| |
Replace test-nonflaky with test-ci and enable verbose output
in all remaining CIs except Zuul which is customized a lot.
Reviewed-by: Daniel Stenberg
Reviewed-by: Jay Satiro
Follow up to #7785
Closes #7832
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Automatically add hacktoberfest-accepted label to PRs opened between
September 30th and November 1st once a commit with a close reference
to it is pushed onto the master branch.
With this workflow we can participate in Hacktoberfest while not
relying on GitHub to identify PRs as merged due to our rebasing.
Requires hacktoberfest-accepted labels to exist for PRs on the
participating repository. Also requires hacktoberfest topic on
the participating repository to avoid applying to forked repos.
Reviewed-by: Daniel Stenberg
Fixes #7865
Closes #7897
|
|
|
|
|
|
|
|
|
|
| |
Make it easy to use the same set of test flags
throughout all current and future CI builds.
Reviewed-by: Jay Satiro
Follow up to #7690
Closes #7785
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Enable codeql writing security-events.
GitHub set the default permissions to read, apparently since earlier
this year.
Ref: https://github.com/github/codeql-action/issues/464
Ref: https://github.blog/changelog/2021-04-20-github-actions-control-permissions-for-github_token/
Fixes https://github.com/curl/curl/issues/7575
Closes https://github.com/curl/curl/pull/7576
|
|
|
|
|
|
| |
As it lists disabled ones in DISABLED now
Closes #7209
|
|
|
|
| |
500 to 512
|
|
|
|
| |
Closes #7205
|
|
|
|
| |
Closes #7206
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Warning: this will make existing curl command lines that use metalink to
stop working.
Reasons for removal:
1. We've found several security problems and issues involving the
metalink support in curl. The issues are not detailed here. When
working on those, it become apparent to the team that several of the
problems are due to the system design, metalink library API and what
the metalink RFC says. They are very hard to fix on the curl side
only.
2. The metalink usage with curl was only very briefly documented and was
not following the "normal" curl usage pattern in several ways, making
it surprising and non-intuitive which could lead to further security
issues.
3. The metalink library was last updated 6 years ago and wasn't so
active the years before that either. An unmaintained library means
there's a security problem waiting to happen. This is probably reason
enough.
4. Metalink requires an XML parsing library, which is complex code (even
the smaller alternatives) and to this day often gets security
updates.
5. Metalink is not a widely used curl feature. In the 2020 curl user
survey, only 1.4% of the responders said that they'd are using it. In
2021 that number was 1.2%. Searching the web also show very few
traces of it being used, even with other tools.
6. The torrent format and associated technology clearly won for
downloading large files from multiple sources in parallel.
Cloes #7176
|
|
|
|
|
|
|
| |
They're too similar to the gcc-9 ones to be useful (and seems to not
work anymore).
Closes #7187
|
|
|
|
|
| |
Assisted-by: Marc Hoersken
Closes #7173
|
|
|
|
|
|
|
| |
... as they otherwise cause ldap build errors in the CI.
Fixes #7081
Closes #7082
|
|
|
|
| |
Closes #7047
|
|
|
|
| |
Closes #6985
|
|
|
|
| |
Closes #6979
|
| |
|
|
|
|
|
|
| |
Makes the option more explicit.
Closes #6887
|
|
|
|
|
|
| |
Extends the CodeQL code scan.
Closes #6815
|
|
|
|
|
|
| |
and at 20% to try to keep the run-time reasonable
Closes #6728
|
|
|
|
|
|
| |
`git checkout HEAD^2` is no longer needed
Closes #6369
|
|
|
|
|
|
|
|
| |
This reverts commit 4cbb17a2cbbbe6337142d39479e21c3990b9c22f.
... as the work-around now causes failures.
Closes #6332
|
|
|
|
| |
Closes #6172
|
|
|
|
|
|
|
| |
... and make it use OpenSSL 1.1 properly
Fixes #6130
Closes #6129
|
|
|
|
|
|
|
|
| |
Remove CURLALTSVC_IMMEDIATELY, which was never implemented/supported.
alt-svc support in curl is no longer considered experimental
Closes #5868
|
|
|
|
|
|
| |
... since github adds an entry automatically by itself.
Closes #5970
|
|
|
|
|
|
|
| |
This helps us to avoid getting feature requests as well as security
bugs reported into the issue tracker.
Closes #5936
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The CMake option is now called CMAKE_USE_SCHANNEL
The winbuild flag is USE_SCHANNEL
The CI jobs and build scripts only use the new names and the new name
options
Tests now require 'Schannel' (when necessary)
Closes #5795
|
|
|
|
|
|
|
| |
This enables some deprecation warnings.
Previously, autotools defaulted to 10.8.
Closes https://github.com/curl/curl/pull/5723
|
|
|
|
| |
Closes https://github.com/curl/curl/pull/5716
|
|
|
|
|
|
| |
Previously, warnings were only visible in the output for most jobs.
Closes https://github.com/curl/curl/pull/5694
|
|
|
|
|
|
|
|
|
|
| |
Align CodeQL action with existing CI actions:
- Update branch filter to avoid duplicate CI runs.
- Shorten workflow name due to informative job name.
Reviewed-by: Daniel Stenberg
Closes #5660
|
|
|
|
| |
It needs a 'with:' in front of it.
|
|
|
| |
enables code security scanning with github actions
|
|
|
|
|
|
| |
Avoid failing CI builds due to nghttp2 being already installed.
Closes #5513
|
| |
|
| |
|
|
|
|
|
|
|
| |
Avoid double-builds when using "local" branches for PRs. For both macos
and fuzz jobs.
Closes #5201
|
|
|
|
| |
Closes #5174
|
|
|
|
|
| |
We are already running a very similar Ubuntu build on Travis CI.
The macOS variant of this default build is kept on Github Actions.
|
|
|
|
| |
Update YAML formatting, job naming and triggers.
|
|
|
|
|
|
|
|
|
| |
Reduce workload on Azure Pipelines and Travis CI while
consolidating macOS jobs onto less utilized GitHub Actions.
Reviewed-by: Daniel Stenberg
Closes #5124
|
|
|
|
|
|
| |
Follow-up from #4960: now make it fail if it detects problems.
Closes #4998
|