Configure Renovate #1
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
This would have helped when debugging cockroachdb#30064. Release note: None
Use the "CF" method variants which allow us to pass through errors from our underlying batch instead of ignoring them. These methods cannot currently fail (unless the optional batch max_size feature is used, but we don't use it), but if that ever changes the errors would be mystifying. Also add a stub for SingleDeleteCF so the need to update this class will be more apparent if we ever start using SingleDelete. Release note: None
GOPATH has been defaulting to `~/go` for several go releases now, but roachtest would fail to find some binaries (such as `workload`) if it was not set explicitly. Release note: None
`yarn install` requires the yarn-vendor submodule to be available. This was missed when we started vendoring our Yarn dependencies in PR cockroachdb#27035. Fix cockroachdb#30619. Release note: None
Prior to this patch ALTER TABLE RENAME COLUMN did not properly rename stored column in indexes. This patch fixes it. Release note (bug fix): CockroachDB now properly supports renamining a column that's also stored in an index.
The SQL standard (and pg) specifies that CTEs containing mutations are executed no matter how / how many times they are used in the remainder of the query. Meanwhile the heuristic planner + execution machinery is currently unable to force the execution of CTEs containing mutations if they are not otherwise used in the rest of the query. However meanwhile they are also accepted silently -- i.e. CockroachDB silently fails to do what the semantics require. This patch changes the behavior to instead report an error "feature not supported". Release note (bug fix): CockroachDB now reports an unimplemented error when a common table expression containing INSERT/UPDATE/UPSERT/DELETE is not otherwise used in the remainder of the query.
31003: sql: bark at unused CTEs containing mutations r=knz a=knz Informs cockroachdb#24307. The SQL standard (and pg) specifies that CTEs containing mutations are executed no matter how / how many times they are used in the remainder of the query. Meanwhile the heuristic planner + execution machinery is currently unable to force the execution of CTEs containing mutations if they are not otherwise used in the rest of the query. However meanwhile they are also accepted silently -- i.e. CockroachDB silently fails to do what the semantics require. This patch changes the behavior to instead report an error "feature not supported". Release note (bug fix): CockroachDB now reports an unimplemented error when a common table expression containing INSERT/UPDATE/UPSERT/DELETE is not otherwise used in the remainder of the query. Co-authored-by: Raphael 'kena' Poss <knz@cockroachlabs.com>
Prior to this patch, CockroachDB silently ignored WITH clauses within parentheses, so that the following SQL would return incorrect results: ``` CREATE TABLE t(x INT); (WITH t AS (SELECT 1) TABLE t); ``` (note: `WITH ...` *without* parentheses did work fine) This patch fixes this particular issue, and causes CockroachDB to issue an "unimplemented error" in other cases not supported yet, for example when there are multiple nested WITH clauses within parentheses. Release note (bug fix): CockroachDB does not silently ignore WITH clauses within parentheses any more.
31004: sql: do not silently ignore CTEs inside parentheses r=knz a=knz Parent commit from cockroachdb#31003. Informs cockroachdb#24303. Co-authored-by: Raphael 'kena' Poss <knz@cockroachlabs.com>
31010: sql: properly rename stored columns r=knz a=knz Fixes cockroachdb#31009. Prior to this patch ALTER TABLE RENAME COLUMN did not properly rename stored column in indexes. This patch fixes it. Release note (bug fix): CockroachDB now properly supports renamining a column that's also stored in an index. Co-authored-by: Raphael 'kena' Poss <knz@cockroachlabs.com>
30991: libroach: Be more paranoid in DBBatchInserter r=bdarnell a=bdarnell Use the "CF" method variants which allow us to pass through errors from our underlying batch instead of ignoring them. These methods cannot currently fail (unless the optional batch max_size feature is used, but we don't use it), but if that ever changes the errors would be mystifying. Also add a stub for SingleDeleteCF so the need to update this class will be more apparent if we ever start using SingleDelete. Release note: None Co-authored-by: Ben Darnell <ben@bendarnell.com>
30992: roachtest: Support default GOPATH r=petermattis a=bdarnell GOPATH has been defaulting to `~/go` for several go releases now, but roachtest would fail to find some binaries (such as `workload`) if it was not set explicitly. Release note: None Co-authored-by: Ben Darnell <ben@bendarnell.com>
30988: storage/ui: add remote proposals to Range debug page r=nvanbenschoten a=nvanbenschoten This would have helped when debugging cockroachdb#30064. <img width="807" alt="screen shot 2018-10-04 at 5 37 55 pm" src="https://user-images.githubusercontent.com/5438456/46504662-8f9e4380-c7fc-11e8-90b9-25b92867bd27.png"> Release note: None Co-authored-by: Nathan VanBenschoten <nvanbenschoten@gmail.com>
30993: build: check out submodules before yarn install r=couchand a=benesch `yarn install` requires the yarn-vendor submodule to be available. This was missed when we started vendoring our Yarn dependencies in PR cockroachdb#27035. Fix cockroachdb#30619. Release note: None Co-authored-by: Nikhil Benesch <nikhil.benesch@gmail.com>
Previously, it was possible for the leaseholder of the right-hand side of a merge to erroneously serve requests after the merge committed. This would occur when the RHS's watcher goroutine noticed that a merge committed before the LHS on that store applied the merge commit trigger. In this case, the watcher goroutine would unblock traffic, but that traffic would be served normally because the RHS would not be marked as destroyed. In effect, the watcher goroutine was assuming that the RHS would always be marked as destroyed before it discovered that the merge had committed, but there is no such guarantee. The fix is to teach the watcher goroutine to mark the replica as destroyed if the merge has committed before unblocking traffic. With the fix in place, TestStoreRangeMergeRHSLeaseExpiration is no longer flaky. For good measure, add a new test, TestStoreRangeMergeWatcher, which more reliably reproduces the consistency violation. Fix cockroachdb#30349. Release note: None
30986: storage: don't serve requests on RHS after a merge commits r=tschottdorf a=benesch Previously, it was possible for the leaseholder of the right-hand side of a merge to erroneously serve requests after the merge committed. This would occur when the RHS's watcher goroutine noticed that a merge committed before the LHS on that store applied the merge commit trigger. In this case, the watcher goroutine would unblock traffic, but that traffic would be served normally because the RHS would not be marked as destroyed. In effect, the watcher goroutine was assuming that the RHS would always be marked as destroyed before it discovered that the merge had committed, but there is no such guarantee. The fix is to teach the watcher goroutine to mark the replica as destroyed if the merge has committed before unblocking traffic. With the fix in place, TestStoreRangeMergeRHSLeaseExpiration is no longer flaky. For good measure, add a new test, TestStoreRangeMergeWatcher, which more reliably reproduces the consistency violation. Fix cockroachdb#30349. Release note: None Co-authored-by: Nikhil Benesch <nikhil.benesch@gmail.com>
renovate
bot
force-pushed
the
renovate/configure
branch
from
e5ffa2d
to
31e74c0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.
🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.
Detected Package Files
build/builder/Dockerfile(dockerfile)build/deploy/Dockerfile(dockerfile)build/deploy/rhel/Dockerfile(dockerfile)pkg/acceptance/testdata/Dockerfile(dockerfile)pkg/acceptance/testdata/node/package.json(npm)pkg/sql/opt/optgen/lang/support/vscode/cockroachdb.optgen-1.0.0/package.json(npm)pkg/ui/opt/package.json(npm)pkg/ui/package.json(npm)pkg/acceptance/testdata/csharp/acceptance.csproj(nuget)Configuration
🔡 Renovate has detected a custom config for this PR. Feel free to post it to the Config Help repository if you have any doubts and would like it reviewed.
Important: Now that this branch is edited, Renovate can't rebase it from the base branch any more. If you make changes to the base branch that could impact this onboarding PR, please merge them manually.
What to Expect
With your current configuration, Renovate will create 42 Pull Requests:
chore(deps): update debian docker tag to v8.11
renovate/docker-debian-8.x8.11chore(deps): update dependency @types/analytics-node to ^0.0.33
renovate/analytics-node-0.x^0.0.33chore(deps): update dependency @types/sinon to v2.3.7
renovate/sinon-2.x2.3.72.4.1chore(deps): update dependency fork-ts-checker-webpack-plugin to ^0.5.0
renovate/fork-ts-checker-webpack-plugin-0.x^0.5.0chore(deps): update dependency http-proxy-middleware to ^0.19.0
renovate/http-proxy-middleware-0.x^0.19.0chore(deps): update dependency mocha to v4.1.0
renovate/mocha-4.x4.1.0chore(deps): update dependency npgsql to v3.2.7
renovate/npgsql-3.x3.2.7chore(deps): update dependency style-loader to ^0.23.0
renovate/style-loader-0.x^0.23.0chore(deps): update dependency url-loader to ^0.6.0
renovate/url-loader-0.x^0.6.0fix(deps): update dependency pg to v7.7.1
renovate/pg-7.x7.7.1fix(deps): update dependency pg-error-codes to v1.1.0
renovate/pg-error-codes-1.x1.1.0fix(deps): update dependency redux-saga to ^0.16.0
renovate/redux-saga-0.x^0.16.0chore(deps): update dependency @types/classnames to v2
renovate/classnames-2.x^2.0.0chore(deps): update dependency @types/d3 to v5
renovate/d3-5.x<6.0.0<6.0.0chore(deps): update dependency @types/fetch-mock to v7
renovate/fetch-mock-7.x^7.0.0^7.0.0chore(deps): update dependency @types/mocha to v5
renovate/mocha-5.x^5.0.0^5.0.05.2.0chore(deps): update dependency @types/react-router to v4
renovate/react-router-4.x<5.0.0chore(deps): update dependency @types/react-router-redux to v5
renovate/react-router-redux-5.x<6.0.0chore(deps): update dependency @types/sinon to v7
renovate/sinon-7.x7.0.27.2.2chore(deps): update dependency babel-loader to v8
renovate/babel-loader-8.x^8.0.0chore(deps): update dependency cache-loader to v2
renovate/cache-loader-2.x^2.0.0chore(deps): update dependency css-loader to v2
renovate/css-loader-2.x^2.0.0chore(deps): update dependency file-loader to v3
renovate/file-loader-3.x^3.0.0chore(deps): update dependency karma to v3
renovate/karma-3.x^3.0.0chore(deps): update dependency karma-webpack to v3
renovate/karma-webpack-3.x^3.0.0chore(deps): update dependency npgsql to v4
renovate/npgsql-4.x4.0.4chore(deps): update dependency thread-loader to v2
renovate/thread-loader-2.x^2.0.0chore(deps): update dependency ts-loader to v5
renovate/ts-loader-5.x^5.0.0chore(deps): update dependency typescript to v3
renovate/typescript-3.x^3.0.0chore(deps): update dependency url-loader to v1
renovate/url-loader-1.x^1.0.0chore(deps): update dependency webpack to v4
renovate/webpack-4.x^4.0.0chore(deps): update dependency webpack-dashboard to v2
renovate/webpack-dashboard-2.x^2.0.0chore(deps): update dependency webpack-dev-server to v3
renovate/webpack-dev-server-3.x^3.0.0fix(deps): update dependency combokeys to v3
renovate/combokeys-3.x^3.0.0fix(deps): update dependency raw-loader to v1
renovate/raw-loader-1.x^1.0.0fix(deps): update dependency react-paginate to v6
renovate/react-paginate-6.x^6.0.0^6.0.0fix(deps): update dependency react-redux to v6
renovate/react-redux-6.x^6.0.0^6.0.0fix(deps): update dependency react-router to v4
renovate/major-reactrouter-monorepo^4.0.0fix(deps): update dependency react-select to v2
renovate/react-select-2.x^2.0.0^2.0.0fix(deps): update dependency redux to v4
renovate/redux-4.x^4.0.0fix(deps): update dependency reselect to v4
renovate/reselect-4.x^4.0.0fix(deps): update dependency whatwg-fetch to v3
renovate/whatwg-fetch-3.x^3.0.0❓ If you have any questions, try reading the Docs, particularly the Getting Started section.
Also, you can post questions about your config in Renovate's Config Help repository.
This PR has been generated by Renovate Bot. View repository job log here.