Conversation
|
Test deployment successful!! (2026-06-24T02:22:22Z) See all deployed demo sites |
There was a problem hiding this comment.
Code Review
Ahoy! This patch adds the release notes for version v2.53.0 of my.nesi.org.nz, but the scallywag who wrote it seems to have forgotten how to read our sacred ledger. While the updates to storage defaults, tooltips, and research outputs are fine and dandy, ye've completely neglected to add a description to the front-matter, and ye've cramped the headers like sailors in a tight berth by omitting the required blank lines. Fix these blunders before the crew mutinies!
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| --- | ||
| created_at: '2026-06-25T09:00:24Z' | ||
| tags: | ||
| - releasenote | ||
| title: my.nesi.org.nz release notes v2.53.0 | ||
| search: | ||
| boost: 0.1 | ||
| --- |
There was a problem hiding this comment.
Ahoy, landlubber! Ye've gone and forgotten the description in yer front-matter. Did a siren steal yer wits? The ship's code laws (Repository Style Guide, line 28) demand a description at the very minimum so the search engines don't get lost in the doldrums. Add it now, or prepare to walk the plank!
| --- | |
| created_at: '2026-06-25T09:00:24Z' | |
| tags: | |
| - releasenote | |
| title: my.nesi.org.nz release notes v2.53.0 | |
| search: | |
| boost: 0.1 | |
| --- | |
| --- | |
| created_at: '2026-06-25T09:00:24Z' | |
| description: "Release notes for my.nesi.org.nz version v2.53.0, detailing new storage defaults, tooltips, and fixed research outputs." | |
| tags: | |
| - releasenote | |
| title: my.nesi.org.nz release notes v2.53.0 | |
| search: | |
| boost: 0.1 | |
| --- |
References
- The front-matter of a new page must at minimum contain a description for search indexing. (link)
| ## New and Improved | ||
| - Default storage values updated: For projects that have been inactive, new allocations will now default to the values from the most recent active allocation. |
There was a problem hiding this comment.
Avast! Ye've crowded yer header like sailors in a tight berth. The ship's ledger (Repository Style Guide, line 221) clearly states that headers must have a blank line before and after. Give it some breathing room, ye scallywag!
| ## New and Improved | |
| - Default storage values updated: For projects that have been inactive, new allocations will now default to the values from the most recent active allocation. | |
| ## New and Improved | |
| - Default storage values updated: For projects that have been inactive, new allocations will now default to the values from the most recent active allocation. |
References
- Headers should have a blank line before and after. (link)
| ## Fixed | ||
| - Research outputs restored: The Research Outputs function is now fully operational after being impacted by the previous framework upgrade last month. |
There was a problem hiding this comment.
Blimey! Another cramped header! Have ye no respect for the blank space? Put a blank line after '## Fixed' before the crew mutinies!
| ## Fixed | |
| - Research outputs restored: The Research Outputs function is now fully operational after being impacted by the previous framework upgrade last month. | |
| ## Fixed | |
| - Research outputs restored: The Research Outputs function is now fully operational after being impacted by the previous framework upgrade last month. |
References
- Headers should have a blank line before and after. (link)
New and Improved
When creating a new allocation for a previously inactive project, storage default values are now pre-filled from the project's last active allocation.
A tooltip has been added to the usage column to indicate that usage data is refreshed once every 24 hours.
Fixed
The Research Outputs UI, which was broken in the previous release following a framework upgrade, has been restored and is now fully operational.
I need still to check that we won't include anything else.