Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Release availability advisories are persisted and rendered as English sentences (Updates tab, de viewers)

Closed
#6,540 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

A pull request for this has already been merged.

  • #6547 by @rbuergi — merged

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp, json

Research direction

Read src/MeshWeaver.PluginCatalog/ReleaseAvailability.cs, PublishedBundleCatalogue.cs, and memex/Memex.Portal.Shared/SelfUpdate/ReleaseAvailabilityService.cs, then trace how UpdatePolicySettingsTab renders content.Advisories and how strings.{en,de}.json is used. The issue proposes persisting structured reasons and localizing them at render time, while keeping English log messages; decide how the proposal fits the existing string workflow and verify German viewers see localized advisories. An open linked pull request (#6547) indicates work is already underway.

Written by the indexing model from the issue text.

Description

bug sev:M

What

Package availability reasons (src/MeshWeaver.PluginCatalog/ReleaseAvailability.cs, PublishedBundleCatalogue.cs, memex/Memex.Portal.Shared/SelfUpdate/ReleaseAvailabilityService.cs) are built as English sentences, persisted as such on Admin/UpdatePolicy (Advisories), and rendered verbatim on the Updates tab (UpdatePolicySettingsTab appends content.Advisories). A German viewer reads them in English. AGENTS.md: platform-owned text follows the VIEWER, so this is a hard-coded UI string.

Shape of a fix (not established, a proposal)

Persist a structured reason (a code from an open string-constant vocabulary, plus its arguments: package, module, identity, target) beside or instead of the sentence, and localize at render time through strings.{en,de}.json. The log line can keep the English sentence.

Evidence / scope

Raised in review of Systemorph/MeshWeaver#6531 (thread on ReleaseAvailability.cs), which only rewords these sentences; the English-only persistence predates that PR. Not measured on a running portal with a de viewer — the rendering path was read in source only.

Refs #6531

Dominant language
C#
Stars
12
Forks
5
Avg merge
4h 19m
Merged PRs (30d)
932

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Systemorph/MeshWeaver

All issues in Systemorph/MeshWeaver

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.