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
37 changes: 37 additions & 0 deletions docs/release_notes/2026_03_18.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
---

Check warning on line 1 in docs/release_notes/2026_03_18.md

View workflow job for this annotation

GitHub Actions / Check page meta

minimum_tags

'tags' property in meta is missing or malformed.

Check warning on line 1 in docs/release_notes/2026_03_18.md

View workflow job for this annotation

GitHub Actions / Check page meta

meta.siblings

Parent category 'release_notes' has too many children (21). Try to keep number of items in a category under '8', maybe add some new categories?
title: 18 March 2026
description: "AGDR release notes for 18 March 2026"
---

## Versions

- Dictionary: 2025_09_01
- Submission (sheepdog): v2026.02
- Portal: production-7.2.3-2026.02
- AGDR Internal helm chart: 1.3
- REMS: 1.0


Copy link
Contributor

Choose a reason for hiding this comment

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

medium

There is an extra blank line here between the main versions list and the micro-services list. Using a single blank line for separation is more conventional and improves source readability. Please consider removing this superfluous line.

### Internal micro-services and more

Check warning on line 15 in docs/release_notes/2026_03_18.md

View workflow job for this annotation

GitHub Actions / Check page meta

walk_toc

Header 'Internal micro-services and more' is too long. Try to keep it under 32 characters to avoid word wrapping in the toc.

Check warning on line 15 in docs/release_notes/2026_03_18.md

View workflow job for this annotation

GitHub Actions / Check page meta

walk_toc

Header 'Internal micro-services and more' is a useless only-child. Give it siblings or remove it.

- gen3-helm chart: 0.2.13
- indexd: 2026.02

Check warning on line 18 in docs/release_notes/2026_03_18.md

View workflow job for this annotation

GitHub Actions / Check Spelling

spelling

Word 'indexd' is misspelled.
- fence: 2026.02
- arborist: 2026.02

Check warning on line 20 in docs/release_notes/2026_03_18.md

View workflow job for this annotation

GitHub Actions / Check Spelling

spelling

Word 'arborist' is misspelled.
- peregrine: 2026.02
- sheepdog: 2026.02
- guppy: 2026.02
- Elasticsearch: elasticsearch-oss:7.10.2

Check warning on line 24 in docs/release_notes/2026_03_18.md

View workflow job for this annotation

GitHub Actions / Check Spelling

spelling

Word 'oss' is misspelled.

Check warning on line 24 in docs/release_notes/2026_03_18.md

View workflow job for this annotation

GitHub Actions / Check Spelling

spelling

Word 'elasticsearch' is misspelled.
- nginx (revproxy): 2026.02

Check warning on line 25 in docs/release_notes/2026_03_18.md

View workflow job for this annotation

GitHub Actions / Check Spelling

spelling

Word 'revproxy' is misspelled.

Check warning on line 25 in docs/release_notes/2026_03_18.md

View workflow job for this annotation

GitHub Actions / Check Spelling

spelling

Word 'nginx' is misspelled.
- tube: 2026.02
- spark: 2026.02
- manifestservice: 2026.02

Check warning on line 28 in docs/release_notes/2026_03_18.md

View workflow job for this annotation

GitHub Actions / Check Spelling

spelling

Word 'manifestservice' is misspelled.
- metadata: production-1.2.2-2026.02
- postgres: 16.4.0

Check warning on line 30 in docs/release_notes/2026_03_18.md

View workflow job for this annotation

GitHub Actions / Check Spelling

spelling

Word 'postgres' is misspelled.

Note: *JupyterHub* is excluded as not used in AGDR.


Copy link
Contributor

Choose a reason for hiding this comment

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

medium

Similar to a previous comment, there is an extra blank line here. For consistency and cleaner source code, it's recommended to use only a single blank line to separate sections.

## New and Improved

Copy link
Contributor

Choose a reason for hiding this comment

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

medium

This line consists only of whitespace characters. While many Markdown parsers treat this as a blank line, it's best practice to use a truly empty line for this purpose. This avoids ambiguity and potential issues with tools that trim trailing whitespace.

- REMS integrated to manage applications for access and submission
Loading