Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found
Select Git revision

Target

Select target project
  • smartdatalab/public/applications/renovate
1 result
Select Git revision
Show changes
Commits on Source (1000)
Showing
with 399 additions and 82 deletions
FROM mcr.microsoft.com/vscode/devcontainers/typescript-node:0.149.0-14@sha256:7ed76ef32b22aa80680443e77ca993008f4e464cac9226a678f97b16cfa2e75c
FROM containerbase/buildpack@sha256:8d0bd58e02d271304e6ab378aede3927dd2cfb98cdae59d0e8bf6f66a5393963
# see https://mcr.microsoft.com/v2/vscode/devcontainers/typescript-node/tags/list for tags
# Add missing renovate dev tools
RUN DEBIAN_FRONTEND=noninteractive apt-get update \
&& apt-get -y install --no-install-recommends --no-upgrade build-essential \
&& rm -rf /var/lib/apt/lists/*
# renovate: datasource=docker versioning=docker
RUN install-tool node 14.16.1 \
# renovate: datasource=npm
&& install-tool yarn 1.22.10
\ No newline at end of file
// For format details, see https://aka.ms/vscode-remote/devcontainer.json or this file's README at:
// https://github.com/microsoft/vscode-dev-containers/tree/v0.106.0/containers/typescript-node-12
{
"name": "Node.js 12 & TypeScript",
"name": "Node.js 14",
"dockerFile": "Dockerfile",
"settings": {
"terminal.integrated.shell.linux": "/bin/bash"
......
......@@ -16,7 +16,6 @@ module.exports = {
'plugin:@typescript-eslint/recommended-requiring-type-checking',
'plugin:promise/recommended',
'prettier',
'prettier/@typescript-eslint',
],
parserOptions: {
ecmaVersion: 9,
......@@ -42,7 +41,7 @@ module.exports = {
'prefer-destructuring': 0,
'prefer-template': 0,
'no-underscore-dangle': 0,
'no-negated-condition': 'error',
'sort-imports': [
'error',
{
......
*.md @HonkingGoose
/lib/manager/git-submodules/ @JamieMagee
/lib/platform/azure/ @JamieMagee
/lib/platform/gitea/ @ppmathis
---
name: Bug report
about: You've found a bug with Renovate
labels: 'type:bug, status:requirements, priority-5-triage'
---
<!--
PLEASE DO NOT REPORT ANY SECURITY CONCERNS THIS WAY
Email renovate-disclosure@whitesourcesoftware.com instead.
-->
**What Renovate type, platform and version are you using?**
<!-- Tell us if you're using the hosted App, or if you are self-hosted Renovate yourself. Platform too (GitHub, GitLab, etc) plus which version of Renovate if you're self-hosted. -->
......@@ -16,14 +22,27 @@ about: You've found a bug with Renovate
<!--
Try not to raise a bug report unless you've looked at the logs first.
If you're running self-hosted, run with `--log-level=debug` or LOG_LEVEL=debug and search for whatever dependency/branch/PR that is causing the problem. If you are using the Renovate App, log into https://app.renovatebot.com/dashboard and locate the correct job log for when the problem occurred (e.g. when the PR was created).
If you're running self-hosted, run with `LOG_LEVEL=debug` in your environment variables and search for whatever dependency/branch/PR that is causing the problem. If you are using the Renovate App, log into https://app.renovatebot.com/dashboard and locate the correct job log for when the problem occurred (e.g. when the PR was created).
Paste the *relevant* logs here, not the entire thing and not just a link to the dashboard (others do not have permissions to view them).
-->
**To Reproduce**
<details><summary>Click me to see logs</summary>
```
Copy/paste any log here, between the starting and ending backticks
```
</details>
**Have you created a minimal reproduction repository?**
Please read the [minimal reproductions documentation](https://github.com/renovatebot/renovate/blob/master/docs/development/minimal-reproductions.md) to learn how to make a good minimal reproduction repository.
<!-- To fix a bug, we usually need a *minimal* public repository to reproduce it in, before verifying that our fix works using the same repo. If you provide a public repo that already reproduces the problem, then your bug will get highest priority for fixing. If you can't reproduce it in a simple repo, do your best to describe how it could be reproduced, or under what circumstances the bug occurs, but it's possible that nobody will start work on it if there's no way to reproduce it without a lot of work. -->
- [ ] I have provided a minimal reproduction repository
- [ ] I don't have time for that, but it happens in a public repository I have linked to
- [ ] I don't have time for that, and cannot share my private repository
- [ ] The nature of this bug means it's impossible to reproduce publicly
**Additional context**
......
blank_issues_enabled: false
contact_links:
- name: Start a discussion (config, doubts, docs)
url: https://github.com/renovatebot/renovate/discussions/new
about: If you have any questions about bot configuration or doubts about whether you should create a feature request or bug report, or have problems with the documentation please click here to create a Discussion instead of an Issue.
---
name: Configuration help
about: Please create an issue in renovatebot/config-help instead
---
Stop!
Configuration help questions for Renovate are very welcome! However, please raise them in the https://github.com/renovatebot/config-help repository instead.
Maybe you might already find your question answered there by a past issue. If not, please [create a new issue](https://github.com/renovatebot/config-help/issues/new).
---
name: Feature request
about: Suggest an idea for this project
labels: 'type:feature, status:requirements, priority-5-triage'
---
**What would you like Renovate to be able to do?**
......
......@@ -3,11 +3,11 @@
## Security
If you think you've found a **security issue**, please do not mention it in this repository.
Instead, email security@renovatebot.com with as much details as possible so that it can be handled confidentially.
Instead, email renovate-disclosure@whitesourcesoftware.com with as much details as possible so that it can be handled confidentially.
## Support
If you have a **configuration question**, please create an issue in https://github.com/renovatebot/config-help
If you want help with your Renovate configuration, go to the [discussions tab in the Renovate repository](https://github.com/renovatebot/renovate/discussions) and open a new "config help" discussion post.
## Bug Reports and Feature Requests
......@@ -26,10 +26,16 @@ Pull Requests can only be merged once all status checks are green, which means `
## Do not force push to your pull request branch
Please do not force push to your PR's branch after you have created your PR, as doing so makes it harder for us to review your work.
Please do not force push to your PR's branch after you have created your PR, as doing so forces us to review the whole PR again.
This makes it harder for us to review your work because we don't know what has changed.
PRs will always be squashed by us when we merge your work.
Commit as many times as you need in your pull request branch.
Force pushing a PR is OK when:
- you need to make large changes on a PR which require a full review anyway
- you need to bring the branch up-to-date with the default branch and incorporating the changes is more work than to create a new PR
## Re-requesting a review
Please do not ping your reviewer(s) by mentioning them in a new comment.
......@@ -41,8 +47,8 @@ Read more about this in the [GitHub docs, Re-requesting a review](https://docs.g
Sometimes the codebase can be a challenge to navigate, especially for a first-time contributor.
We don't want you spending an hour trying to work out something that would take us only a minute to explain.
For that reason, we have a Slack channel dedicated to helping anyone who's working on Pull Requests for Renovate.
Please email rhys@renovatebot.com and simply mention that you need an invitation to the channel.
For that reason, we have a Slack channel dedicated to helping anyone who's working on or considering Pull Requests for Renovate.
Please email rhys@arkins.net and simply mention that you need an invitation to the channel and you'll be added ASAP.
## Legal
......
'reproduction:needed':
comment: >
Hi there,
The Renovate team needs your help!
Before we can start work on your issue we first need to know exactly what's causing the current behavior.
A minimal reproduction helps us with this.
To get started, please read our guide on [minimal reproductions](https://github.com/renovatebot/renovate/blob/master/docs/development/minimal-reproductions.md) to understand what is needed.
We may close the issue if you have not provided a minimal reproduction within two weeks.
If you need more time, or are stuck, please ask for help or more time in a comment.
Good luck,
The Renovate team
'reproduction:provided':
comment: >
Thank you for providing a reproduction! :tada: :rocket:
The Renovate team will take a look at the reproduction repository.
Once we confirm the provided repository reproduces the problem, the label will be changed to `reproduction:confirmed`.
'logs:problem':
comment: >
Hi there,
We have found that there's a problem with the logs.
Depending on which situation applies follow one, some or all of these instructions.
### No logs at all
If there's no log posted yet, we need you to find and copy/paste the log into the issue template.
#### Finding logs on hosted app
<details><summary>Click me to read instructions</summary>
If you use the Renovate app (GitHub):
1. Go to the affected PR, and search for "View repository job log here"
1. Click on the link to go to the "WhiteSource Renovate Dashboard" and log in
1. You are now in the correct repository log overview screen
1. Copy/paste the correct log
1. Follow the steps in the **formatting your logs** section
</details>
#### Finding logs when self-hosting
<details><summary>Click me to read instructions</summary>
If you're running self-hosted, run with `LOG_LEVEL=debug` in your environment variables and search for whatever dependency/branch/PR that is causing the problem.
</details>
### Insufficient logs
<details><summary>Click me to read instructions</summary>
If you already provided logs, and the Renovate team said they are not enough, follow the instructions from the **No logs at all** section.
</details>
### Formatting your logs
<details><summary>Click me to read instructions</summary>
Please put your logs in a `<details>` and `<summary>` element like this:
<details><summary>Click me to see logs</summary>
```
Copy/paste any log here, between the starting and ending backticks
```
</details>
</details>
......@@ -3,7 +3,7 @@
## Changes:
<!-- Describe what this pull request changes. -->
<!-- Describe what behavior is changed by this PR. -->
## Context:
......@@ -21,9 +21,10 @@ I have verified these changes via:
- [ ] Code inspection only, or
- [ ] Newly added unit tests, or
- [ ] Unit tests + ran on a real repository
- [ ] No new tests but ran on a real repository, or
- [ ] Both unit tests + ran on a real repository
<!-- Do you have any suggestions about this PR template? Edit it here: https://github.com/renovatebot/renovate/edit/master/.github/pull_request_template.md -->
<!-- Please do not force push to this PR's branch after you have created this PR, as doing so makes it harder for us to review your work. -->
<!-- Please do not force push to your PR's branch after you have created your PR, as doing so forces us to review the whole PR again. This makes it harder for us to review your work because we don't know what has changed. -->
<!-- PRs will always be squashed by us when we merge your work. Commit as many times as you need in this branch. -->
name: build-pr
on:
pull_request:
env:
YARN_MODULES_CACHE_KEY: v1
YARN_PACKAGE_CACHE_KEY: v1
YARN_CACHE_FOLDER: .cache/yarn
NODE_VERSION: 14
PYTHON_VERSION: 3.8
SKIP_JAVA_TESTS: true
jobs:
test:
runs-on: ubuntu-latest
# tests shouldn't need more time
timeout-minutes: 30
steps:
- name: Set up Node.js ${{ env.NODE_VERSION }}
uses: actions/setup-node@v2.1.5
with:
node-version: ${{ env.NODE_VERSION }}
- name: Set up Python ${{ env.PYTHON_VERSION }}
uses: actions/setup-python@v2.2.2
with:
python-version: ${{ env.PYTHON_VERSION }}
- name: Init platform
shell: bash
run: |
git config --global core.autocrlf false
git config --global core.symlinks true
git config --global user.email 'renovate@whitesourcesoftware.com'
git config --global user.name 'Renovate Bot'
npm config set scripts-prepend-node-path true
echo "Node $(node --version)"
python --version
echo "Yarn $(yarn --version)"
- uses: actions/checkout@v2.3.4
with:
fetch-depth: 2
- name: Cache Yarn packages
id: yarn_cache_packages
uses: actions/cache@v2.1.5
with:
path: ${{ env.YARN_CACHE_FOLDER }}
key: ${{ env.YARN_PACKAGE_CACHE_KEY }}-${{ runner.os }}-yarn_cache-${{ hashFiles('**/yarn.lock') }}
restore-keys: |
${{ env.YARN_PACKAGE_CACHE_KEY }}-${{ runner.os }}-yarn_cache-
# Clear caches on cache miss, otherwise they will grow indefinitely
- name: Clear yarn cache
if: steps.yarn_cache_packages.outputs.cache-hit != 'true'
run: yarn cache clean
- name: Installing dependencies
run: yarn install --frozen-lockfile
- name: Unit tests
run: yarn jest --logHeapUsage --maxWorkers=2 --ci
- name: Codecov
uses: codecov/codecov-action@v1.3.2
if: always()
# build after tests to exclude files
- name: Build
run: yarn build
- name: E2E Test
run: yarn test-e2e
lint:
runs-on: ubuntu-latest
# lint shouldn't need more than 10 min
timeout-minutes: 15
steps:
- name: Set up Node.js ${{ env.NODE_VERSION }}
uses: actions/setup-node@v2.1.5
with:
node-version: ${{ env.NODE_VERSION }}
- name: Init platform
run: |
git config --global core.autocrlf false
git config --global core.symlinks true
git config --global user.email 'renovate@whitesourcesoftware.com'
git config --global user.name 'Renovate Bot'
npm config set scripts-prepend-node-path true
echo "Node $(node --version)"
echo "Yarn $(yarn --version)"
- uses: actions/checkout@v2.3.4
- name: Cache Yarn packages
id: yarn_cache_packages
uses: actions/cache@v2.1.5
with:
path: ${{ env.YARN_CACHE_FOLDER }}
key: ${{ env.YARN_PACKAGE_CACHE_KEY }}-${{ runner.os }}-yarn_cache-${{ hashFiles('**/yarn.lock') }}
restore-keys: |
${{ env.YARN_PACKAGE_CACHE_KEY }}-${{ runner.os }}-yarn_cache-
# Clear caches on cache miss, otherwise they will grow indefinitely
- name: Clear yarn cache
if: steps.yarn_cache_packages.outputs.cache-hit != 'true'
run: yarn cache clean
- name: Installing dependencies
run: yarn install --frozen-lockfile
- name: Lint
run: |
yarn ls-lint
yarn eslint
yarn prettier
- name: Test schema
run: yarn test-schema
- name: Type check
run: yarn type-check
......@@ -4,17 +4,14 @@ on:
push:
branches:
- master
- 'renovate/**'
pull_request:
workflow_dispatch:
env:
YARN_MODULES_CACHE_KEY: v1
YARN_PACKAGE_CACHE_KEY: v1
YARN_CACHE_FOLDER: .cache/yarn
NODE_VERSION: 12
# https://github.com/chalk/supports-color/issues/106
FORCE_COLOR: true
NODE_VERSION: 14
jobs:
test:
......@@ -26,38 +23,35 @@ jobs:
strategy:
matrix:
os: [ubuntu-latest, macos-latest, windows-latest]
node-version: [12, ^14.15.0]
node-version: [14]
python-version: [3.8]
java-version: [8]
exclude:
- os: windows-latest
node-version: 10
java-version: [11]
env:
coverage: ${{ matrix.os == 'ubuntu-latest' && matrix.node-version == 12 }}
coverage: ${{ matrix.os == 'ubuntu-latest' && matrix.node-version == 14 }}
NODE_VERSION: ${{ matrix.node-version }}
PYTHON_VERSION: ${{ matrix.python-version }}
JAVA_VERSION: ${{ matrix.java-version }}
steps:
- name: Set up Node.js ${{ env.NODE_VERSION }}
uses: actions/setup-node@v1.4.4
uses: actions/setup-node@v2.1.5
with:
node-version: ${{ env.NODE_VERSION }}
- name: Set up Python ${{ env.PYTHON_VERSION }}
uses: actions/setup-python@v2.1.4
uses: actions/setup-python@v2.2.2
with:
python-version: ${{ env.PYTHON_VERSION }}
- name: Set up Java ${{ env.JAVA_VERSION }}
if: env.NODE_VERSION == '12'
if: env.NODE_VERSION == '14'
uses: actions/setup-java@v1.4.3
with:
java-version: ${{ env.JAVA_VERSION }}
- name: Skip Java tests
if: env.NODE_VERSION != '12'
if: env.NODE_VERSION != '14'
run: echo "SKIP_JAVA_TESTS=true" >> $GITHUB_ENV
- name: Init platform
......@@ -73,10 +67,12 @@ jobs:
echo "Yarn $(yarn --version)"
- uses: actions/checkout@v2.3.4
with:
fetch-depth: 2
- name: Cache Yarn packages
id: yarn_cache_packages
uses: actions/cache@v2.1.3
uses: actions/cache@v2.1.5
with:
path: ${{ env.YARN_CACHE_FOLDER }}
key: ${{ env.YARN_PACKAGE_CACHE_KEY }}-${{ runner.os }}-yarn_cache-${{ hashFiles('**/yarn.lock') }}
......@@ -91,26 +87,16 @@ jobs:
- name: Installing dependencies
run: yarn install --frozen-lockfile
- name: Build
run: yarn build
- name: Unit tests
run: yarn jest --maxWorkers=2 --ci --coverage ${{ env.coverage }}
- name: Upload coverage
uses: actions/upload-artifact@v2.2.0
if: always() && env.coverage == 'true'
with:
name: coverage
path: coverage
run: yarn jest --logHeapUsage --maxWorkers=2 --ci --coverage ${{ env.coverage }}
- name: Codecov
shell: bash
uses: codecov/codecov-action@v1.3.2
if: always() && env.coverage == 'true'
continue-on-error: true
run: bash <(curl -s https://codecov.io/bash)
env:
CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
# build after tests to exclude files
- name: Build
run: yarn build
- name: E2E Test
run: yarn test-e2e
......@@ -123,7 +109,7 @@ jobs:
steps:
- name: Set up Node.js ${{ env.NODE_VERSION }}
uses: actions/setup-node@v1.4.4
uses: actions/setup-node@v2.1.5
with:
node-version: ${{ env.NODE_VERSION }}
......@@ -141,7 +127,7 @@ jobs:
- name: Cache Yarn packages
id: yarn_cache_packages
uses: actions/cache@v2.1.3
uses: actions/cache@v2.1.5
with:
path: ${{ env.YARN_CACHE_FOLDER }}
key: ${{ env.YARN_PACKAGE_CACHE_KEY }}-${{ runner.os }}-yarn_cache-${{ hashFiles('**/yarn.lock') }}
......@@ -158,6 +144,7 @@ jobs:
- name: Lint
run: |
yarn ls-lint
yarn eslint -f ./tmp/tools/eslint-gh-reporter.js
yarn prettier
......@@ -175,7 +162,7 @@ jobs:
steps:
- name: Set up Node.js ${{ env.NODE_VERSION }}
uses: actions/setup-node@v1.4.4
uses: actions/setup-node@v2.1.5
with:
node-version: ${{ env.NODE_VERSION }}
......@@ -194,7 +181,7 @@ jobs:
fetch-depth: 0
- name: Cache Yarn packages
uses: actions/cache@v2.1.3
uses: actions/cache@v2.1.5
with:
path: ${{ env.YARN_CACHE_FOLDER }}
key: ${{ env.YARN_PACKAGE_CACHE_KEY }}-${{ runner.os }}-yarn_cache-${{ hashFiles('**/yarn.lock') }}
......
......@@ -16,15 +16,6 @@ jobs:
steps:
- name: Checkout repository
uses: actions/checkout@v2.3.4
with:
# We must fetch at least the immediate parents so that if this is
# a pull request then we can checkout the head.
fetch-depth: 2
# If this run was triggered by a pull request event, then checkout
# the head of the pull request instead of the merge commit.
- run: git checkout HEAD^2
if: ${{ github.event_name == 'pull_request' }}
# Initializes the CodeQL tools for scanning.
- name: Initialize CodeQL
......
name: 'Label Actions'
on:
issues:
types: [labeled]
jobs:
reaction:
runs-on: ubuntu-latest
steps:
- uses: dessant/label-actions@v2
with:
github-token: ${{ github.token }}
process-only: 'issues'
name: lock-threads
on:
# run daily
schedule:
- cron: '0 0 * * *'
# allow manual trigger
workflow_dispatch:
jobs:
lock:
runs-on: ubuntu-latest
steps:
- uses: dessant/lock-threads@v2.0.3
if: github.repository == 'renovatebot/renovate'
with:
github-token: ${{ github.token }}
issue-lock-inactive-days: 30
pr-lock-inactive-days: 30
......@@ -7,16 +7,14 @@ env:
YARN_MODULES_CACHE_KEY: v1
YARN_PACKAGE_CACHE_KEY: v1
YARN_CACHE_FOLDER: .cache/yarn
NODE_VERSION: 12
# https://github.com/chalk/supports-color/issues/106
FORCE_COLOR: true
NODE_VERSION: 14
jobs:
release-npm:
runs-on: ubuntu-latest
steps:
- name: Set up Node.js ${{ env.NODE_VERSION }}
uses: actions/setup-node@v1.4.4
uses: actions/setup-node@v2.1.5
with:
node-version: ${{ env.NODE_VERSION }}
......@@ -35,7 +33,7 @@ jobs:
- name: Cache Yarn packages
id: yarn_cache_packages
uses: actions/cache@v2.1.3
uses: actions/cache@v2.1.5
with:
path: ${{ env.YARN_CACHE_FOLDER }}
key: ${{ env.YARN_PACKAGE_CACHE_KEY }}-${{ runner.os }}-yarn_cache-${{ hashFiles('**/yarn.lock') }}
......
# Go to https://github.com/actions/stale for the full documentation of these options.
name: 'Close stale bug reports that lack reproduction'
on:
schedule:
- cron: '30 1 * * *'
jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v3.0.18
with:
# Rate limit per run, (defaults to 30, but we've increased it to 40 for now).
operations-per-run: 40
# Only issues with both `reproduction:needed` and `type:bug` will be touched by the stale bot.
only-issue-labels: 'reproduction:needed,type:bug'
# A issue that has any assignee is getting worked on, so is exempt from stale bot.
exempt-all-issue-assignees: true
# Remove stale label from issue/PR on updates or comments, defaults to true.
remove-stale-when-updated: true
# Wait 14 days until making issue stale and posting a message.
days-before-issue-stale: 14
stale-issue-message: 'When a bug has been marked as needing a reproduction, it means nobody can work on it until one is provided. In cases where no reproduction is possible, or the issue creator does not have the time to reproduce, we unfortunately need to close such issues as they are non-actionable and serve no benefit by remaining open. This issue will be closed after 7 days of inactivity.'
stale-issue-label: 'stale'
# Close out issue after 7 stale days.
days-before-issue-close: 7
close-issue-message: 'This bug report has been closed as we need a reproduction to work on this. If the original poster or anybody else with the same problem discovers that they can reproduce it, please create a new issue, and reference this issue.'
name: whitesource-scan
on:
push:
branches: [master]
jobs:
WS_SCAN:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2.3.4
- name: Download UA
run: curl -LJO https://github.com/whitesource/unified-agent-distribution/releases/latest/download/wss-unified-agent.jar
- name: Run UA scan
run: java -jar wss-unified-agent.jar -d $GITHUB_WORKSPACE -noConfig true -apiKey ${{ secrets.WS_ORG_TOKEN }} -product W4D -project "Renovate OS - master" -resolveAllDependencies false -npm_resolveDependencies true
......@@ -23,3 +23,5 @@ renovate-schema.json
tools/dist
test/datasource/nuget/_fixtures/obj
# testing
/docker-compose.yml