Issue
Contribution records

This contribution record is for a security advisory.

Contributors

Granted credits are reviewed by maintainers. Learn more about granting credit.

Give credit to everyone
berdir organization(s): MD Systems GmbH
chi
David_Rothstein volunteering
heine organization(s): ronder
schnitzel organization(s): amazee.io
agentrickard organization(s): Palantir.net
gg4
cashwilliams organization(s): Acquia
catch organization(s): Third and Grove
cilefen volunteering
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
droplet
GrandmaGlassesRopeMan organization(s): Acquia
effulgentsia organization(s): Acquia
greggles
larowlan organization(s): PreviousNext customer(s): Charles Darwin University
logaritmisk
mpdonadio organization(s): DiD Agency
plach organization(s): Tag1 Consulting, Inc.
pwolanin volunteering organization(s): SciShield
sugaroverflow
tedbow organization(s): Acquia
tstoeckler volunteering
will_c
xjm organization(s): Acquia
gábor hojtsy organization(s): Acquia
wim leers organization(s): Acquia
samuel.mortenson organization(s): Acquia
stefan.r
tim.plunkett organization(s): Acquia
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit
  • task: A planned operational or maintenance change to the codebase

See the format of the Git commit message.

Copy and paste the message in the Merge UI screen or commit message. If needed, improve the title after you paste. The message follows conventional commits format.