Bump eslint from 7.22.0 to 7.29.0

.dockerignore

@@ -5,4 +5,5 @@ node_modules
 coverage
 .buildkite
 *.pem
-.git
+.git
+dist/

.eslintignore

@@ -1 +1,3 @@
-coverage
+coverage
+dist/
+node_modules/

.github/dependabot.yml

@@ -0,0 +1,27 @@
+version: 2
+updates:
+  - package-ecosystem: docker
+    directory: '/'
+    schedule:
+      interval: daily
+    open-pull-requests-limit: 10
+  - package-ecosystem: npm
+    directory: '/'
+    schedule:
+      interval: daily
+    open-pull-requests-limit: 10
+    labels:
+      - 'type: dependencies'
+    ignore:
+      - dependency-name: '@hapi/joi'
+        versions:
+          - '>= 16.a'
+          - '< 18'
+      - dependency-name: '@types/hapi__joi'
+        versions:
+          - '>= 16.a'
+          - '< 18'
+  - package-ecosystem: 'github-actions'
+    directory: '/'
+    schedule:
+      interval: 'daily'

.github/no-unstaged-files.sh

@@ -0,0 +1,7 @@
+#!/bin/bash
+
+if [[ "$(git status --porcelain)" != "" ]]; then
+  git status
+  echo "::error::💥 Unstaged changes detected. Locally try running: yarn prettier && yarn lint --fix && yarn build"
+  exit 1
+fi

.github/release-drafter.yml

@@ -32,3 +32,6 @@ version-resolver:
       - 'type: docs'
       - 'type: dependencies'
       - 'type: security'
+
+exclude-labels:
+  - 'skip-changelog'

.github/workflows/rebase.yml

@@ -1,24 +1,26 @@
 on:
   issue_comment:
-    types: [created]
+    types:
+      - created
 name: Automatic Rebase
 jobs:
   rebase:
     name: Rebase
-    if: github.event.issue.pull_request != '' && contains(github.event.comment.body, '/rebase')
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@master
+      - uses: khan/pull-request-comment-trigger@master
+        id: check
+        with:
+          trigger: '/rebase'
+          reaction: rocket
+        env:
+          GITHUB_TOKEN: '${{ secrets.GITHUB_TOKEN }}'
+      - uses: actions/checkout@v2
+        if: steps.check.outputs.triggered == 'true'
         with:
           fetch-depth: 0
       - name: Automatic Rebase
-        uses: cirrus-actions/[email protected]
+        uses: cirrus-actions/[email protected]
+        if: steps.check.outputs.triggered == 'true'
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-  # https://github.community/t5/GitHub-Actions/Workflow-is-failing-if-no-job-can-be-ran-due-to-condition/m-p/38186#M3250
-  always_job:
-    name: Always run job
-    runs-on: ubuntu-latest
-    steps:
-      - name: Always run
-        run: echo "This job is used to prevent the workflow to fail when all other jobs are skipped."

.github/workflows/tests.yml

@@ -1,16 +1,24 @@
 name: Tests
 
-on: [push, pull_request]
+on:
+  push:
+    branches:
+      - master
+  pull_request:
 
 jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@master
-      - uses: actions/setup-node@v1
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v2
         with:
-          version: 13.x
-      - name: Test
-        run: |
-          yarn install
-          yarn test
+          node-version: '13'
+      - run: yarn install --frozen-lockfile
+      - run: yarn test
+      - run: yarn lint --fix
+      - run: yarn prettier
+      - run: yarn build
+      - name: correct vercel/ncc crlf output
+        run: sed -i 's/\x0D$//' ./dist/index.js
+      - run: .github/no-unstaged-files.sh

.gitignore

@@ -6,3 +6,5 @@ coverage
 now.json
 docker-compose-logs
 package-lock.json
+dist/static/
+dist/views/

.prettierignore

@@ -1 +1,3 @@
 config-with-yaml-exception.yml
+dist/
+coverage/

.prettierrc

@@ -1,4 +1,6 @@
 {
+  "trailingComma": "es5",
+  "arrowParens": "always",
   "semi": false,
   "singleQuote": true,
   "bracketSpacing": true

.vscode/settings.json

@@ -1,6 +1,8 @@
 {
-  "eslint.autoFixOnSave": true,
   "editor.codeActionsOnSave": {
     "source.fixAll.eslint": true
+  },
+  "files.exclude": {
+    "dist/": true
   }
 }

Dockerfile

@@ -1,4 +1,4 @@
-FROM node:14.4.0-alpine@sha256:796fbe3509bdd36aef0e62508379f84e32a172062b7a37cb3609dee1567893b9
+FROM node:15.11.0-alpine@sha256:1aa4d551d84797a2df6261e4b6a78b849f6bd11b0dc94b7f2ddf0023fecd8261
 ARG NODE_ENV=production
 ENV NODE_ENV=${NODE_ENV}
 LABEL "repository"="https://github.com/toolmantim/release-drafter"
@@ -11,4 +11,5 @@ LABEL "com.github.actions.color"="orange"
 WORKDIR /app
 COPY . .
 RUN yarn --frozen-lockfile
-ENTRYPOINT [ "/app/node_modules/.bin/probot", "receive", "/app/index.js" ]
+ENTRYPOINT [ "/app/node_modules/.bin/probot" ]
+CMD [ "receive", "/app/index.js" ]

README.md

@@ -18,16 +18,26 @@ on:
     # branches to consider in the event; optional, defaults to all
     branches:
       - master
+  # pull_request event is required only for autolabeler
+  pull_request:
+    # Only following types are handled by the action, but one can default to all as well
+    types: [opened, reopened, synchronize]
 
 jobs:
   update_release_draft:
     runs-on: ubuntu-latest
     steps:
+      # (Optional) GitHub Enterprise requires GHE_HOST variable set
+      #- name: Set GHE_HOST
+      #  run: |
+      #    echo "GHE_HOST=${GITHUB_SERVER_URL##https:\/\/}" >> $GITHUB_ENV
+
       # Drafts your next Release notes as Pull Requests are merged into "master"
       - uses: release-drafter/release-drafter@v5
-        with:
-          # (Optional) specify config name to use, relative to .github/. Default: release-drafter.yml
-          # config-name: my-config.yml
+        # (Optional) specify config name to use, relative to .github/. Default: release-drafter.yml
+        # with:
+        #   config-name: my-config.yml
+        #   disable-autolabeler: true
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 ```
@@ -96,6 +106,7 @@ You can configure Release Drafter using the following key in your `.github/relea
 | Key                    | Required | Description                                                                                                                                                                |
 | ---------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `template`             | Required | The template for the body of the draft release. Use [template variables](#template-variables) to insert values.                                                            |
+| `category-template`    | Optional | The template to use for each category. Use [category template variables](#category-template-variables) to insert values. Default: `"## $TITLE"`.                           |
 | `name-template`        | Optional | The template for the name of the draft release. For example: `"v$NEXT_PATCH_VERSION"`.                                                                                     |
 | `tag-template`         | Optional | The template for the tag of the draft release. For example: `"v$NEXT_PATCH_VERSION"`.                                                                                      |
 | `version-template`     | Optional | The template to use when calculating the next version number for the release. Useful for projects that don't use semantic versioning. Default: `"$MAJOR.$MINOR.$PATCH"`    |
@@ -111,6 +122,8 @@ You can configure Release Drafter using the following key in your `.github/relea
 | `sort-direction`       | Optional | Sort changelog in ascending or descending order. Can be one of: `ascending`, `descending`. Default: `descending`.                                                          |
 | `prerelease`           | Optional | Mark the draft release as pre-release. Default `false`.                                                                                                                    |
 | `version-resolver`     | Optional | Adjust the `$RESOLVED_VERSION` variable using labels. Refer to [Version Resolver](#version-resolver) to learn more about this                                              |
+| `filter-by-commitish`  | Optional | Filter previous releases to consider only the target branch of the release. Default: `false`.                                                                              |
+| `commitish`            | Optional | Specify the target branch of the release. Default: the default branch of the repo.                                                                                         |
 
 Release Drafter also supports [Probot Config](https://github.com/probot/probot-config), if you want to store your configuration files in a central repository. This allows you to share configurations between projects, and create a organization-wide configuration file by creating a repository named `.github` with the file `.github/release-drafter.yml`.
 
@@ -124,6 +137,14 @@ You can use any of the following variables in your `template`:
 | `$CONTRIBUTORS` | A comma separated list of contributors to this release (pull request authors, commit authors, and commit committers). |
 | `$PREVIOUS_TAG` | The previous releases’s tag.                                                                                          |
 
+## Category Template Variables
+
+You can use any of the following variables in `category-template`:
+
+| Variable | Description                          |
+| -------- | ------------------------------------ |
+| `$TITLE` | The category title, e.g. `Features`. |
+
 ## Next Version Variables
 
 You can use any of the following variables in your `template`, `name-template` and `tag-template`:
@@ -133,7 +154,7 @@ You can use any of the following variables in your `template`, `name-template` a
 | `$NEXT_PATCH_VERSION` | The next patch version number. For example, if the last tag or release was `v1.2.3`, the value would be `v1.2.4`. This is the most commonly used value. |
 | `$NEXT_MINOR_VERSION` | The next minor version number. For example, if the last tag or release was `v1.2.3`, the value would be `v1.3.0`.                                       |
 | `$NEXT_MAJOR_VERSION` | The next major version number. For example, if the last tag or release was `v1.2.3`, the value would be `v2.0.0`.                                       |
-| `$RESOLVED_VERSION`   | The next resolved version number, based on GitHub labels. Refer to [Version Resolution](#version-resolution) to learn more about this.                  |
+| `$RESOLVED_VERSION`   | The next resolved version number, based on GitHub labels. Refer to [Version Resolver](#version-resolver) to learn more about this.                      |
 
 ## Version Template Variables
 
@@ -213,7 +234,8 @@ Pull requests with the label "feature" or "fix" will now be grouped together:
 
 <img src="design/screenshot-2.png" alt="Screenshot of generated draft release with categories" width="586" />
 
-Adding such labels to your PRs can be automated by using [PR Labeler](https://github.com/TimonVS/pr-labeler-action) or [Probot Auto Labeler](https://github.com/probot/autolabeler).
+Adding such labels to your PRs can be automated by using the embedded Autolabeler functionality (see below),
+[PR Labeler](https://github.com/TimonVS/pr-labeler-action) or [Probot Auto Labeler](https://github.com/probot/autolabeler).
 
 ## Exclude Pull Requests
 
@@ -249,6 +271,30 @@ replacers:
     replace: 'My Name'
 ```
 
+## Autolabeler
+
+You can add automatically a label into a pull request, with the `autolabeler` option. Available matchers are `files` (glob), `branch` (regex), `title` (regex) and `body` (regex).
+Matchers are evaluated independently; the label will be set if at least one of the matchers meets the criteria.
+
+```yml
+autolabeler:
+  - label: 'chore'
+    files:
+      - '*.md'
+    branch:
+      - '/docs{0,1}\/.+/'
+  - label: 'bug'
+    branch:
+      - '/fix\/.+/'
+    title:
+      - '/fix/i'
+  - label: 'enhancement'
+    branch:
+      - '/feature\/.+/'
+    body:
+      - '/JIRA-[0-9]{1,4}/'
+```
+
 ## Projects that don't use Semantic Versioning
 
 If your project doesn't follow [Semantic Versioning](https://semver.org) you can still use Release Drafter, but you may want to set the `version-template` option to customize how the `$NEXT_{PATCH,MINOR,MAJOR}_VERSION` environment variables are generated.
@@ -267,6 +313,7 @@ The Release Drafter GitHub Action accepts a number of optional inputs directly i
 | `version`     | The version to be associated with the GitHub release that's created or updated. This will override any version calculated by the release-drafter.                                                                                                                                                                                                                  |
 | `publish`     | A boolean indicating whether the release being created or updated should be immediately published. This may be useful if the output of a previous workflow step determines that a new version of your project has been (or will be) released, as with [`salsify/action-detect-and-tag-new-version`](https://github.com/salsify/action-detect-and-tag-new-version). |
 | `prerelease`  | A boolean indicating whether the relase being created or updated is a prerelease.                                                                                                                                                                                                                                                                                  |
+| `commitish`   | A string specifying the target branch for the release being created.                                                                                                                                                                                                                                                                                               |
 
 ## Action Outputs
 

action.js

@@ -0,0 +1,7 @@
+const core = require('@actions/core')
+const { run } = require('@probot/adapter-github-actions')
+const app = require('./index')
+
+run(app).catch((err) => {
+  core.setFailed(`💥 Release drafter failed with error: ${err.message}`)
+})

action.yml

@@ -1,8 +1,8 @@
 name: 'Release Drafter'
 description: 'Drafts your next release notes as pull requests are merged into master.'
 runs:
-  using: 'docker'
-  image: 'Dockerfile'
+  using: 'node12'
+  main: 'dist/index.js'
 branding:
   icon: edit-2
   color: orange
@@ -35,7 +35,22 @@ inputs:
     default: ''
   prerelease:
     description: |
-      A boolean indicating whether the relase being created or updated is a prerelease.
+      A boolean indicating whether the release being created or updated is a prerelease.
+    required: false
+    default: ''
+  commitish:
+    description: |
+      The object that the release should be created to point to.
+    required: false
+    default: ''
+  disable-releaser:
+    description: |
+      A boolean indicating whether the releaser mode is disabled.
+    required: false
+    default: ''
+  disable-autolabeler:
+    description: |
+      A boolean indicating whether the autolabeler mode is disabled.
     required: false
     default: ''
 outputs:

bin/generate-schema.js

@@ -13,7 +13,13 @@ const jsonSchema = {
 }
 
 // template is only required after deep merged, should not be required in the JSON schema
-jsonSchema.required = jsonSchema.required.filter((item) => item !== 'template')
+// we should also remove the required field in case nothing remains after the filtering to keep draft04 compatibility
+const requiredField = jsonSchema.required.filter((item) => item !== 'template')
+if (requiredField.length) {
+  jsonSchema.required = requiredField
+} else {
+  delete jsonSchema.required
+}
 
 if (args[0] === 'print') {
   fs.writeFileSync('./schema.json', `${JSON.stringify(jsonSchema, null, 2)}\n`)