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

memex CLI not on nuget.org: 3-latest is 3.1.10990, MeshWeaver.Cli 3.1.10990 is not listed

Open
#6,845 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-3 hours
Newbie friendliness
12/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp, github-actions
Domain
ci-cd, release

Research direction

This is a release-process alert, not a code change. The issue is generated by .github/scripts/cli-publish-alert.sh and says not to edit its body, so any fix belongs in the script or in publishing. Read Doc/Architecture/NuGetPackageRetirement §1a and publish-packages.yml. Done means MeshWeaver.Cli 3.1.10990 is listed on nuget.org, or the alert closes itself on the next run. Publishing needs maintainer access.

Written by the indexing model from the issue text.

Description

bug cli-publish-failure feature:release-promotion sev:M

3-latest names 3.1.10990, and nuget.org does not list MeshWeaver.Cli 3.1.10990, with no publication of it in flight. dotnet tool install -g MeshWeaver.Cli therefore does not give the CLI of the build the fleet runs.

Reconciled by https://github.com/Systemorph/MeshWeaver/actions/runs/38870695092 at 2026-10-16T08:30:28Z.

Publish it: gh workflow run publish-packages.yml --ref main -f version=3.1.10990 -f ref=<the core commit of that build> -f packages=cli, or let the next arming publish a newer one.


Maintained by .github/scripts/cli-publish-alert.sh, which derives this issue from those two facts on every CLI publication and every arming (Doc/Architecture/NuGetPackageRetirement §1a). It closes itself once they agree. Do not edit the body — edit the script.

Dominant language
C#
Stars
12
Forks
5
Avg merge
5h 44m
Merged PRs (30d)
968

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.