Release v1.14.2

[aharwood2]

This pull request introduces several significant updates across the codebase, focusing on project and person data models, CI workflow improvements, and dependency/tooling updates. The most impactful changes include enhancements to the Project and Person entities to better support project request tracking and access control, the addition of new test steps and workflow triggers in CI, and updates to dependencies and GitHub Actions for improved maintainability and security.

Entity Model Enhancements:

• Added new properties to the Project entity for tracking creation date, request completion date, request owner, and a navigation property to the owner (CreatedDate, RequestCompletedDate, RequestOwnerId, RequestOwner) and implemented logic to determine if an active user has edit access to a project. Also added a method to check for funding sources not linked to resources, and made DayRateWithDIFunding() public. [1] [2]
• Updated the Person entity to remove inheritance from ObjectWithStatusMessages, re-architecting the status message system to use DI services instead of entity-based conditions, added a navigation property for projects where the person is the request owner, and introduced a method to get BAU (Business As Usual) capacity on a given date as we now have the ability to track capacity of core teams / baselined teams alongside project work and management load. [1] [2] [3]
• Changed AssignmentChunk to use a string AssignmentType (defaulting to Duty.ProjectWork) instead of a boolean IsLeadershipAssignment, to facilitate different tasks coming from different WLM categories and updated the copy constructor accordingly. [1] [2] [3]
• Removed inheritance from ObjectWithStatusMessages in the CostedItem abstract class as this is no-longer required.

Continuous Integration and Workflow Improvements:

• Added Playwright test steps and .NET setup/restore to the docker-images-build-health-check workflow, enabled manual workflow dispatch, and updated several GitHub Actions to newer versions for better reliability and security. [1] [2] [3] [4] [5] [6]
• Updated workflow job references to use a new commit hash for shared actions and removed the CODEOWNERS file as it was causing a lot of review request noise. [1] [2] [3]

Dependency and Configuration Updates:

• Bumped dotnet-ef tool version from 10.0.9 to 10.0.10 in .config/dotnet-tools.json.
• Refined Dependabot configuration to use more descriptive group names and updated the structure for github-actions ecosystem.

These changes collectively improve the maintainability, test coverage, and feature set of the application, especially around project request tracking and developer workflows.

@sjmf @philiptharrison I'm looking at rolling out the next release 9-10 BST on 8th September 2026 as I'm keen to get the request tracking feature deployed (I realise this is purely selfish!). Is that a reasonable timeframe for you to test the release candidate on your systems? Let me know if not and we can set a different date.

Release contents here: https://github.com/orgs/UoMResearchIT/projects/81/views/2?filterQuery=milestone%3Av1.14.2+is%3Aissue+

[sjmf]

Looking great - thanks for this update.

@sjmf @philiptharrison I'm looking at rolling out the next release 9-10 BST on 8th September 2026 as I'm keen to get the request tracking feature deployed (I realise this is purely selfish!). Is that a reasonable timeframe for you to test the release candidate on your systems? Let me know if not and we can set a different date.

If this has hit dev, our production deployment is already testing it as I rebased my API development branch onto latest dev yesterday to pick up those properties changes you mention. It's showing 1.14.2 in the UI. :)

There's also a potential addition sitting in your Outlook inbox which might warrant inclusion in this release.

[PhilBradbury]

I've seen the email. Who invited Samantha to the party? 🤣

Excellent spot though, and definitely something we need to address both in terms of governance and the code. 👍

[philiptharrison]

@aharwood2 the proposed release schedule is fine for us. We're way behind with everything anyway.