Platform news
-
New ordering of workspaces on OpenSAFELY Jobs homepage
What has changed? Once logged into OpenSAFELY Jobs, the 5 workspaces shown to you on your home page are now the five most recently active (by creation/modification date or most recently run job) that you have access to. This is a change from previously showing you the five most recently…
-
Comparing study code on OpenSAFELY Jobs
OpenSAFELY Jobs has always shown the Git commit hash for a given job request or job, with a link to view the workspace’s code on GitHub as of that revision. We now also provide GitHub code comparison links (example) so you can see exactly what code has changed between…
-
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…
-
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!
-
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 writing their…
-
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 meet the…
-
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 file extension…
-
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. The…
-
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 user’s machines…
-
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:
Subscribe to Platform News updates
Receive an email alert when the OpenSAFELY platform is updated.