Skip to main content

Platform news

  1. Markdown formatting of Project Status Description

    Users can now use Markdown formatting to update the Status Description field in the Project page. Screenshots Example URLs…

  2. ehrQL v1 released

    We have released v1 of ehrQL. It contains a small number of breaking changes from v0. For existing users of ehrQL, please refer to the release notes for guidance about updating from v0. Thank you to all users who have tried out ehrQL and given us feedback!

  3. ehrQL’s measures framework has disclosure control enabled by default

    ehrQL’s measures framework is used to calculate quotients (i.e. a numerator divided by a denominator) and to see how these vary over time and when broken down by different groupings. Previously, numerators and denominators were not subject to disclosure control: a user had to apply disclosure control by…

  4. Warn about invalid moderately_sensitive outputs

    The opensafely tool has been updated to warn you if you have invalid outputs marked as moderately_sensitive in your project.yaml. This is a follow on from the previous change about stricter output file paths and means that you’ll get more accurate feedback when running the code locally. Specifically, it will check that moderately_sensitive outputs…

  5. Stricter output paths in project.yaml

    We’ve made some changes to slightly restrict output file paths. Specifically, all paths must now end with file extension, e.g. .csv. Previously, it was possibly to use a trailing * character to match all files (e.g. outputs/data.*). You can still use * to match groups of similar files, but you must end the pattern with a…

  6. Updated packages in R image

    In order to add a new package to the R Docker image we had to upgrade some of the existing package versions. Hopefully these upgrades will be welcome but there’s a small possibility they might cause issues with existing code so please be on the look out for this.

  7. Automatically run failed dependencies when submitting jobs

    Previously, when submitting jobs to run the platform would reject requests if any of the requested action’s dependencies had previously failed. This required users to explicitly request those failed dependencies to be re-run. This was cumbersome, and was not the same behaviour as when running actions locally on…

  8. Updated disclosure control guidance

    We have recently made some updates to our disclosure control guidance. This is important for both researchers requesting release of outputs and those who review them. We have made the following changes, which are summarised in more detail below:

  9. User, project, and organisation Event Logs added

    OpenSAFELY Jobs has been updated with new Event Log pages for users, projects, and organisations. These pages provide specific information about current Job Requests, and allow users to see a complete audit log of all previous Job Requests. Examples of new Event Log pages include: The…

  10. New opensafely clean command

    We have added a command to the opensafely command line tool: opensafely clean This command will safely remove any leftover OpenSAFELY docker artifacts from your system. Specifically, it removes old images, job containers, and file volumes that may have been created when running jobs locally on a user’s computer.

Subscribe to Platform News updates

Receive an email alert when the OpenSAFELY platform is updated.

What type of news do you want to receive?

You can unsubscribe at any time by clicking the link in the footer of our emails.

We use Mailchimp as our marketing platform. By clicking below to subscribe, you acknowledge that your information will be transferred to Mailchimp for processing.

Learn more about Mailchimp's privacy practices here.