Releases: NHSDigital/validated-relationships-service-api
Releases · NHSDigital/validated-relationships-service-api
v1.0.557-alpha
Task/npa 6618/remove grantee (#336)
# Pull Request
## 🧾 Ticket Link
<!-- Add the Jira ticket link here -->
https://nhsd-jira.digital.nhs.uk/browse/NPA-6618
---
## 📄 Description/Summary of Changes
<!-- Describe the changes made in this PR. Include the
purpose/scope/impact of the changes -->
- Updated OAS Spec to remove any reference to grantee and replace with
performer.
- Updates to examples in OAS for GET Consent and GET Consent/{id}
response examples and POST Consent request examples.
- Update int postman collection.
- Update sandbox and unit tests
---
## 🧪 Developer Testing Carried Out
<!-- Describe what tests (automated/unit/manual etc.) have been done for
the ticket. Include: -->
<!-- - Any tests added/updated -->
<!-- - Evidence that each acceptance criterion from the Jira ticket is
met -->
<!-- - Evidence of tests running eg. link to github workflow with tests
passing or screenshot of tests running locally -->
- <!-- Briefly describe the testing carried out in this PR -->
---
## 📋 PR Principles
<!-- Principles we as a team follow when conducting a PR -->
- Keep PRs Small and Focused: Ensure the PR addresses a single task or
feature to make it easier to review.
- Multiple PRs for one Ticket: When splitting work into multiple PRs,
clearly describe what this PR addresses and outline the remaining work
to complete the ticket.
- Ensure Tests Are Included: Add or update unit, integration, or
end-to-end tests to cover the changes made.
- Follow Coding Standards: Ensure the code adheres to the team's coding
guidelines and best practices.
- Resolve Comments Promptly: If you raise a comment, ensure you follow
up and resolve it before approving the PR to maintain clarity and ensure
comments are addressed.
- Foster Learning: PR reviews are an opportunity to share knowledge,
provide constructive feedback, and encourage a collaborative
environment.
## 🏷️ Naming Conventions Reminder
Please ensure the following naming conventions are followed:
- PR title follows the format: `NPA-XXXX: <short-description>`
- Branch name follows the convention:
`<type>/NPA-XXXX/<short-description>`
- Commit messages follow the template: `NPA-XXXX: <short-description>`
v1.0.556-alpha
NPA-6615: bump OAS version to 1.20.0 for release (#338) # Pull Request ## 🧾 Ticket Link <!-- Add the Jira ticket link here --> https://nhsd-jira.digital.nhs.uk/browse/NPA-6615 --- ## 📄 Description/Summary of Changes <!-- Describe the changes made in this PR. Include the purpose/scope/impact of the changes --> - Spec version bump for the release --- ## 🧪 Developer Testing Carried Out <!-- Describe what tests (automated/unit/manual etc.) have been done for the ticket. Include: --> <!-- - Any tests added/updated --> <!-- - Evidence that each acceptance criterion from the Jira ticket is met --> <!-- - Evidence of tests running eg. link to github workflow with tests passing or screenshot of tests running locally --> - <!-- Briefly describe the testing carried out in this PR --> --- ## 📋 PR Principles <!-- Principles we as a team follow when conducting a PR --> - Keep PRs Small and Focused: Ensure the PR addresses a single task or feature to make it easier to review. - Multiple PRs for one Ticket: When splitting work into multiple PRs, clearly describe what this PR addresses and outline the remaining work to complete the ticket. - Ensure Tests Are Included: Add or update unit, integration, or end-to-end tests to cover the changes made. - Follow Coding Standards: Ensure the code adheres to the team's coding guidelines and best practices. - Resolve Comments Promptly: If you raise a comment, ensure you follow up and resolve it before approving the PR to maintain clarity and ensure comments are addressed. - Foster Learning: PR reviews are an opportunity to share knowledge, provide constructive feedback, and encourage a collaborative environment. ## 🏷️ Naming Conventions Reminder Please ensure the following naming conventions are followed: - PR title follows the format: `NPA-XXXX: <short-description>` - Branch name follows the convention: `<type>/NPA-XXXX/<short-description>` - Commit messages follow the template: `NPA-XXXX: <short-description>`
v1.0.555-alpha
Task/NPA-6616/replace regulatory basis with policy rule (#334)
# Pull Request
## 🧾 Ticket Link
<!-- Add the Jira ticket link here -->
https://nhsd-jira.digital.nhs.uk/browse/NPA-6616
---
## 📄 Description/Summary of Changes
<!-- Describe the changes made in this PR. Include the
purpose/scope/impact of the changes -->
- Remove references to regulatoryBasis and replace it with policyRule.
- Updates to examples in OAS for GET Consent and GET Consent/{id}
response examples, PATCH Consent and POST Consent request examples.
- Updates to the int postman collection
---
## 🧪 Developer Testing Carried Out
<!-- Describe what tests (automated/unit/manual etc.) have been done for
the ticket. Include: -->
<!-- - Any tests added/updated -->
<!-- - Evidence that each acceptance criterion from the Jira ticket is
met -->
<!-- - Evidence of tests running eg. link to github workflow with tests
passing or screenshot of tests running locally -->
- <!-- Briefly describe the testing carried out in this PR -->
---
## 📋 PR Principles
<!-- Principles we as a team follow when conducting a PR -->
- Keep PRs Small and Focused: Ensure the PR addresses a single task or
feature to make it easier to review.
- Multiple PRs for one Ticket: When splitting work into multiple PRs,
clearly describe what this PR addresses and outline the remaining work
to complete the ticket.
- Ensure Tests Are Included: Add or update unit, integration, or
end-to-end tests to cover the changes made.
- Follow Coding Standards: Ensure the code adheres to the team's coding
guidelines and best practices.
- Resolve Comments Promptly: If you raise a comment, ensure you follow
up and resolve it before approving the PR to maintain clarity and ensure
comments are addressed.
- Foster Learning: PR reviews are an opportunity to share knowledge,
provide constructive feedback, and encourage a collaborative
environment.
## 🏷️ Naming Conventions Reminder
Please ensure the following naming conventions are followed:
- PR title follows the format: `NPA-XXXX: <short-description>`
- Branch name follows the convention:
`<type>/NPA-XXXX/<short-description>`
- Commit messages follow the template: `NPA-XXXX: <short-description>`
v1.0.554-alpha
NPA-6521: Investigate hanging sandbox check (#331) # Pull Request ## 🧾 Ticket Link <!-- Add the Jira ticket link here --> https://nhsd-jira.digital.nhs.uk/browse/NPA-6521 --- ## 📄 Description/Summary of Changes <!-- Describe the changes made in this PR. Include the purpose/scope/impact of the changes --> - The job was not showing as completed because some processes in the Flask group weren't being killed at the end of the test run. This change updates the commands to enable job control (`set -m`) which places all the Flask processes in a process group. It then gracefully shuts down all the processes in that process group. - Also deleted the sandbox-check status check for PRs as it references a github action that no longer exists and has been superseded by `test-sandbox-and-postman` <img width="591" height="153" alt="Screenshot 2026-04-13 at 15 51 40" src="https://github.com/user-attachments/assets/9a3941fd-fe08-4f8a-97f9-e553d890fd54" /> --- ## 🧪 Developer Testing Carried Out <!-- Describe what tests (automated/unit/manual etc.) have been done for the ticket. Include: --> <!-- - Any tests added/updated --> <!-- - Evidence that each acceptance criterion from the Jira ticket is met --> <!-- - Evidence of tests running eg. link to github workflow with tests passing or screenshot of tests running locally --> - <!-- Briefly describe the testing carried out in this PR --> --- ## 📋 PR Principles <!-- Principles we as a team follow when conducting a PR --> - Keep PRs Small and Focused: Ensure the PR addresses a single task or feature to make it easier to review. - Multiple PRs for one Ticket: When splitting work into multiple PRs, clearly describe what this PR addresses and outline the remaining work to complete the ticket. - Ensure Tests Are Included: Add or update unit, integration, or end-to-end tests to cover the changes made. - Follow Coding Standards: Ensure the code adheres to the team's coding guidelines and best practices. - Resolve Comments Promptly: If you raise a comment, ensure you follow up and resolve it before approving the PR to maintain clarity and ensure comments are addressed. - Foster Learning: PR reviews are an opportunity to share knowledge, provide constructive feedback, and encourage a collaborative environment. ## 🏷️ Naming Conventions Reminder Please ensure the following naming conventions are followed: - PR title follows the format: `NPA-XXXX: <short-description>` - Branch name follows the convention: `<type>/NPA-XXXX/<short-description>` - Commit messages follow the template: `NPA-XXXX: <short-description>`
v1.0.553-alpha
NPA-6426: Correctly specify and handle FHIR composite search logic fo…
v1.0.552-alpha
NPA-6547: bump OAS version to 1.19.0 (#326) # Pull Request ## 🧾 Ticket Link <!-- Add the Jira ticket link here --> https://nhsd-jira.digital.nhs.uk/browse/NPA-6547 --- ## 📄 Description/Summary of Changes <!-- Describe the changes made in this PR. Include the purpose/scope/impact of the changes --> - Increment version for release --- ## 🧪 Developer Testing Carried Out <!-- Describe what tests (automated/unit/manual etc.) have been done for the ticket. Include: --> <!-- - Any tests added/updated --> <!-- - Evidence that each acceptance criterion from the Jira ticket is met --> <!-- - Evidence of tests running eg. link to github workflow with tests passing or screenshot of tests running locally --> - <!-- Briefly describe the testing carried out in this PR --> --- ## 📋 PR Principles <!-- Principles we as a team follow when conducting a PR --> - Keep PRs Small and Focused: Ensure the PR addresses a single task or feature to make it easier to review. - Multiple PRs for one Ticket: When splitting work into multiple PRs, clearly describe what this PR addresses and outline the remaining work to complete the ticket. - Ensure Tests Are Included: Add or update unit, integration, or end-to-end tests to cover the changes made. - Follow Coding Standards: Ensure the code adheres to the team's coding guidelines and best practices. - Resolve Comments Promptly: If you raise a comment, ensure you follow up and resolve it before approving the PR to maintain clarity and ensure comments are addressed. - Foster Learning: PR reviews are an opportunity to share knowledge, provide constructive feedback, and encourage a collaborative environment. ## 🏷️ Naming Conventions Reminder Please ensure the following naming conventions are followed: - PR title follows the format: `NPA-XXXX: <short-description>` - Branch name follows the convention: `<type>/NPA-XXXX/<short-description>` - Commit messages follow the template: `NPA-XXXX: <short-description>`
v1.0.551-alpha
NPA-6425: auditing error responses (#319) # Pull Request ## 🧾 Ticket Link <!-- Add the Jira ticket link here --> https://nhsd-jira.digital.nhs.uk/browse/NPA-6425 --- ## 📄 Description/Summary of Changes <!-- Describe the changes made in this PR. Include the purpose/scope/impact of the changes --> - This PR matches up the error responses we return from VRS with the Spec. - This involved some error codes changing, and some errors being added/removed - A PR has been raised in the PVRS repo to reflect some of these changes too. --- ## 🧪 Developer Testing Carried Out <!-- Describe what tests (automated/unit/manual etc.) have been done for the ticket. Include: --> <!-- - Any tests added/updated --> <!-- - Evidence that each acceptance criterion from the Jira ticket is met --> <!-- - Evidence of tests running eg. link to github workflow with tests passing or screenshot of tests running locally --> - Tested this spec branch against my PVRS changes to check all tests passing https://github.com/NHSDigital/proxy-validated-relationships-service/pull/1392 --- ## 📋 PR Principles <!-- Principles we as a team follow when conducting a PR --> - Keep PRs Small and Focused: Ensure the PR addresses a single task or feature to make it easier to review. - Multiple PRs for one Ticket: When splitting work into multiple PRs, clearly describe what this PR addresses and outline the remaining work to complete the ticket. - Ensure Tests Are Included: Add or update unit, integration, or end-to-end tests to cover the changes made. - Follow Coding Standards: Ensure the code adheres to the team's coding guidelines and best practices. - Resolve Comments Promptly: If you raise a comment, ensure you follow up and resolve it before approving the PR to maintain clarity and ensure comments are addressed. - Foster Learning: PR reviews are an opportunity to share knowledge, provide constructive feedback, and encourage a collaborative environment. ## 🏷️ Naming Conventions Reminder Please ensure the following naming conventions are followed: - PR title follows the format: `NPA-XXXX: <short-description>` - Branch name follows the convention: `<type>/NPA-XXXX/<short-description>` - Commit messages follow the template: `NPA-XXXX: <short-description>`
v1.0.550-alpha
NPA-6501: bump spec version before release (#318) # Pull Request ## 🧾 Ticket Link <!-- Add the Jira ticket link here --> https://nhsd-jira.digital.nhs.uk/browse/NPA-6501 --- ## 📄 Description/Summary of Changes <!-- Describe the changes made in this PR. Include the purpose/scope/impact of the changes --> - <!-- Briefly describe the key changes in this PR --> --- ## 🧪 Developer Testing Carried Out <!-- Describe what tests (automated/unit/manual etc.) have been done for the ticket. Include: --> <!-- - Any tests added/updated --> <!-- - Evidence that each acceptance criterion from the Jira ticket is met --> <!-- - Evidence of tests running eg. link to github workflow with tests passing or screenshot of tests running locally --> - <!-- Briefly describe the testing carried out in this PR --> --- ## 📋 PR Principles <!-- Principles we as a team follow when conducting a PR --> - Keep PRs Small and Focused: Ensure the PR addresses a single task or feature to make it easier to review. - Multiple PRs for one Ticket: When splitting work into multiple PRs, clearly describe what this PR addresses and outline the remaining work to complete the ticket. - Ensure Tests Are Included: Add or update unit, integration, or end-to-end tests to cover the changes made. - Follow Coding Standards: Ensure the code adheres to the team's coding guidelines and best practices. - Resolve Comments Promptly: If you raise a comment, ensure you follow up and resolve it before approving the PR to maintain clarity and ensure comments are addressed. - Foster Learning: PR reviews are an opportunity to share knowledge, provide constructive feedback, and encourage a collaborative environment. ## 🏷️ Naming Conventions Reminder Please ensure the following naming conventions are followed: - PR title follows the format: `NPA-XXXX: <short-description>` - Branch name follows the convention: `<type>/NPA-XXXX/<short-description>` - Commit messages follow the template: `NPA-XXXX: <short-description>`
v1.0.549-alpha
NPA-6263: Update GET RelatedPerson examples to ensure the patient res…
v1.0.548-alpha
no-ticket: update pr template (#316) # Pull Request ## 🧾 Ticket Link <!-- Add the Jira ticket link here --> https://nhsd-jira.digital.nhs.uk/browse/no-ticket --- ## 📄 Description/Summary of Changes <!-- Describe the changes made in this PR. Include the purpose/scope/impact of the changes --> - Updated pull request template --- ## 🧪 Developer Testing Carried Out <!-- Describe what tests (automated/unit/manual etc.) have been done for the ticket. Include: --> <!-- - Any tests added/updated --> <!-- - Evidence that each acceptance criterion from the Jira ticket is met --> <!-- - Evidence of tests running eg. link to github workflow with tests passing or screenshot of tests running locally --> - <!-- Briefly describe the testing carried out in this PR --> --- ## 📋 PR Principles <!-- Principles we as a team follow when conducting a PR --> - Keep PRs Small and Focused: Ensure the PR addresses a single task or feature to make it easier to review. - Multiple PRs for one Ticket: When splitting work into multiple PRs, clearly describe what this PR addresses and outline the remaining work to complete the ticket. - Ensure Tests Are Included: Add or update unit, integration, or end-to-end tests to cover the changes made. - Follow Coding Standards: Ensure the code adheres to the team's coding guidelines and best practices. - Resolve Comments Promptly: If you raise a comment, ensure you follow up and resolve it before approving the PR to maintain clarity and ensure comments are addressed. - Foster Learning: PR reviews are an opportunity to share knowledge, provide constructive feedback, and encourage a collaborative environment. ## 🏷️ Naming Conventions Reminder Please ensure the following naming conventions are followed: - PR title follows the format: `NPA-XXXX: <short-description>` - Branch name follows the convention: `<type>/NPA-XXXX/<short-description>` - Commit messages follow the template: `NPA-XXXX: <short-description>`