Skip to content

backlog: file the @flashynetwork version-reconciliation blocker - #24

Merged
AgenteLabs merged 3 commits into
mainfrom
backlog-flashynetwork-item
Oct 29, 2026
Merged

AgenteLabs merged 3 commits into
mainfrom
backlog-flashynetwork-item

Conversation

@AgenteLabs

Copy link
Copy Markdown
Owner

Summary

@flashynetwork is now claimed on npm (zero packages published). The estate decided this ledger moves there, but this repo has three disagreeing version numbers for one package: package.json says 1.0.0, ClaimYour.Gold depends on @flashylabs/ledger@^0.8.0 (below what's committed, and that name 404s on public npm — only GitHub Packages has it), and @flashyos/ledger@1.0.1 is live on public npm, published by hand outside this repo's publish.yml, which still only knows how to publish @flashylabs/ledger.

Filed as a blocker-kind backlog/1 item (decays in 14 days, matching the format's own rule that a blocker can't sit stale) rather than left as a comment nobody can query: version reconciliation has to happen before .npmrc/publish.yml can target @flashynetwork/ledger directly, or the rename just adds a fourth number.

Filed via @flashyos/backlog's file(), promoted to public via promote({by: 'person/michael'}), emitted with the repo's own vendor-backlog.mjs emit, validated with check — nothing hand-edited.

Verified

  • node vendor-backlog.mjs check backlog.fragment.json → ok


Generated by Claude Code

Three disagreeing version numbers for one package (this repo's 1.0.0,
ClaimYour.Gold's dependency on ^0.8.0, the live-but-out-of-band
@flashyos/ledger 1.0.1) need reconciling before publish.yml can target
the newly-claimed @FlashyNetwork scope directly. Filed and promoted to
public via @flashyos/backlog's file()/promote(), not hand-edited.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VgrPGGUFKMq9zXBHnfcTgs
…-item

# Conflicts:
#	backlog.fragment.json
#	public/.well-known/backlog.json
The item was filed against a stale, shallow clone that predated commit
c00c482 (2026-10-26), which already did what it asked for a better
reason than I had: the GitHub org rename broke @flashylabs's GitHub
Packages scope resolution, and the fix published @flashyos/ledger
1.0.1 to public npm and updated package.json, .npmrc (removed) and
publish.yml to match. ClaimYour.Gold's dependency is confirmed already
updated too. Closed via revise()/status:done rather than deleted, per
backlog/1's own rule that a correction is appended, never edited away.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VgrPGGUFKMq9zXBHnfcTgs

Copy link
Copy Markdown
Owner Author

Dependency audit failure — confirmed unrelated to this PR

This PR touches only .backlog/items.json, backlog.fragment.json and public/.well-known/backlog.json — no package.json, no lockfile. npm audit --audit-level=high is failing on 4 pre-existing advisories in the vitest/vite/@vitest/coverage-v8/@vitest/mocker devDependency chain (moderate/high severity, dev-tooling only, nothing in the published @flashyos/ledger package itself). Since nothing in this PR's diff touches dependencies, this is a property of the current main dependency tree regardless of this PR, and npm audit fix / a version bump is separate work from filing a backlog item. Not widening this PR to fix it.

Also corrected the item itself in the latest commit: it was filed against a stale clone and wrongly described the ledger's version as unresolved and @flashyos/ledger 1.0.1 as published by hand. Neither was true — see the commit message.


🤖 Generated with Claude Code


Generated by Claude Code

@AgenteLabs
AgenteLabs merged commit 73052e8 into main Oct 29, 2026
11 of 12 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.

2 participants