Skip to content

docs(progress): second real run, releases 0.1.0/0.1.1, resuming locally - #27

Merged
NeyorDEV merged 1 commit into
mainfrom
docs/progress-0.1.1
Oct 21, 2026
Merged

NeyorDEV merged 1 commit into
mainfrom
docs/progress-0.1.1

Conversation

@NeyorDEV

Copy link
Copy Markdown
Owner

Updates PROGRESS.md so the project can be picked up in a new session, local or cloud.

Changes

  • Real-world tests:
  • Known limitations: updated. CurseForge has now been tested with a real key. Resource packs are analysed when a CurseForge export lists them, but not yet inside a .mrpack.
  • Branches & PRs: the workflow since phase 22 is now one branch per fix from main. Also covers how to handle a CHANGELOG conflict between two PRs.
  • Manual actions:
    • steps to publish 0.1.1;
    • the general release procedure;
    • npm prerequisites (dev dependencies, 2FA).
  • Next steps, plus a new "Resuming in a local session" section: git pull, npm ci, claude or claude --teleport.
  • Pitfalls:
    • Nushell on Windows (quotes, $env);
    • README edits require prettier + docs:pages;
    • hash collisions in test fixtures;
    • realistic descriptions for the alternatives tests.
  • Known issues: none blocking (the old branch was deleted).

Documentation only. Prettier is clean.


Generated by Claude Code

… and how to resume locally

Keeps PROGRESS.md the reference for picking the project up in a new
(local) session: what the CurseForge run found and fixed, the release
procedure, the maintainer's shell quirks and the test pitfalls met since.
@NeyorDEV
NeyorDEV merged commit 07fbd27 into main Oct 21, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant