Skip to content

chore: Update security policy#127

Merged
ian-robinson-35 merged 1 commit intomainfrom
chore/update-security-policy
Apr 24, 2026
Merged

chore: Update security policy#127
ian-robinson-35 merged 1 commit intomainfrom
chore/update-security-policy

Conversation

@ian-robinson-35
Copy link
Copy Markdown
Contributor

@ian-robinson-35 ian-robinson-35 commented Apr 24, 2026

Description

Update security policy to latest recommendation, including link to github vulnerability report

Context

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming
  • Exceptions/Exclusions to coding standards (e.g. #noqa or #NOSONAR) are included within this Pull Request.

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@ian-robinson-35 ian-robinson-35 marked this pull request as ready for review April 24, 2026 08:24
@ian-robinson-35 ian-robinson-35 requested review from a team as code owners April 24, 2026 08:24
@sonarqubecloud
Copy link
Copy Markdown

@github-actions
Copy link
Copy Markdown

Deployment Complete

Copy link
Copy Markdown
Collaborator

@nhsd-jack-wainwright nhsd-jack-wainwright left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@ian-robinson-35 ian-robinson-35 merged commit 3db3ebd into main Apr 24, 2026
33 checks passed
@ian-robinson-35 ian-robinson-35 deleted the chore/update-security-policy branch April 24, 2026 09:49
nhsd-rebecca-flynn pushed a commit that referenced this pull request Apr 24, 2026
<!-- markdownlint-disable-next-line first-line-heading -->
## Description

Update security policy to latest recommendation, including link to
github vulnerability report

## Context

<!-- Why is this change required? What problem does it solve? -->

## Type of changes

<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply. -->

- [x] Refactoring (non-breaking change)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would change existing
functionality)
- [ ] Bug fix (non-breaking change which fixes an issue)

## Checklist

<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->

- [x] I have followed the code style of the project
- [ ] I have added tests to cover my changes
- [ ] I have updated the documentation accordingly
- [ ] This PR is a result of pair or mob programming
- [ ] Exceptions/Exclusions to coding standards (e.g. #noqa or #NOSONAR)
are included within this Pull Request.

---

## Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others
privacy, we kindly ask you to NOT including [PII (Personal Identifiable
Information) / PID (Personal Identifiable
Data)](https://digital.nhs.uk/data-and-information/keeping-data-safe-and-benefitting-the-public)
or any other sensitive data in this PR (Pull Request) and the codebase
changes. We will remove any PR that do contain any sensitive
information. We really appreciate your cooperation in this matter.

- [x] I confirm that neither PII/PID nor sensitive data are included in
this PR and the codebase changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants