Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
---
created_at: '2026-05-22T09:00:24Z'
tags:
- releasenote
title: my.nesi.org.nz release notes v2.52.0
search:
boost: 0.1
---
Comment on lines +1 to +8
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

low

Avast! Ye've gone and forgotten the description in yer metadata. I suppose ye expect the search lubbers to just guess what's in this here scroll? The rules clearly state a description is needed at the minimum. It's not like we wrote the guide for our health, ye scurvy dog.

Suggested change
---
created_at: '2026-05-22T09:00:24Z'
tags:
- releasenote
title: my.nesi.org.nz release notes v2.52.0
search:
boost: 0.1
---
---
created_at: '2026-05-22T09:00:24Z'
description: "Release notes for my.nesi.org.nz version 2.52.0, including policy updates and Angular 21 upgrade."
tags:
- releasenote
title: my.nesi.org.nz release notes v2.52.0
search:
boost: 0.1
---
References
  1. The metadata header must at minimum contain a description field. (link)


## New and Improved
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

low

Blimey! Are ye tryin' to save ink? Put a blank line after that header ## New and Improved. It's in the articles of agreement (the style guide, ye scallywag). I know whitespace is a rare treasure, but surely ye can spare a line for the sake of readability.

Suggested change
## New and Improved
## New and Improved
References
  1. Headers should have a blank line before and after. (link)

- The default organisation for allocation requests is now automatically set to the project's organisation.
- my.nesi.org.nz's User Interface (UI) package has been upgraded to Angular 21, improving security and ensuring continued platform support.
- When NeSI integrated with REANNZ on 1 July 2025, responsibility for all aspects of NeSI service delivery, including HPC Platform policies, transferred to REANNZ. To better reflect that transition, we have made some minor administrative updates to our policy documents to:
- Update the organisation name and contact details from NeSI to REANNZ
- Change outdated hyperlinks (e.g. links to service pages, other policies, etc.)
- Publish the updated version in the Policy section of our REANNZ Support Documentation site
These updates are effective immediately and do not change the intent or requirements of the policies. The links to the following policies have been updated:
1. [Access Policy](https://docs.nesi.org.nz/Policy/Access_Policy/)
2. [Acceptable Use Policy](https://docs.nesi.org.nz/Policy/Acceptable_Use_Policy/)
3. [Privacy Policy](https://docs.nesi.org.nz/Policy/Privacy_Policy/)
4. [Security Policy](https://docs.nesi.org.nz/Policy/Security_Policy/)

If you have any questions about any of the updates, please
{% include "partials/support_request.html" %}.
Loading