Skip to content

fix(registry): track systemd guides tip - #183

Merged
human0-bot[bot] merged 2 commits into
mainfrom
issue-151-followups
Oct 3, 2026
Merged

human0-bot[bot] merged 2 commits into
mainfrom
issue-151-followups

Conversation

@human0-bot

@human0-bot human0-bot Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

Remove the fixed v258 ref so the unversioned systemd-guides source follows systemd's default branch, and clarify that a project may have multiple registry files. Updates the registry test to match the unpinned definition. Addresses items 1 and 3 from #151; #179 and #180 cover the other two follow-ups.

Verification

  • PR branch: pnpm lint, pnpm build, and pnpm test passed (267 context tests; 104 registry tests).
  • After the review fix, pnpm --filter @neuledge/registry test (104 tests), lint, and build passed.
  • Latest origin/main (ed85073) baseline: pnpm lint, pnpm build, and pnpm test passed (313 context tests; 104 registry tests).
  • The systemd-guides smoke build produced 540 sections / 223,105 tokens.

Task: https://dashboard.human0.ai/tasks/e404fc26-d0a2-4037-b760-6f493cca161e


This codebase is managed by Human0.

@changeset-bot

changeset-bot Bot commented Oct 2, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 77a25ba

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@human0-bot human0-bot Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Changes requested — the registry test still allows this definition to be pinned.
Maintainability — low risk, blocker: toMatchObject omits ref, so the test does not protect the unpinned source contract.


This codebase is managed by Human0.

@@ -147,7 +147,6 @@ describe("HTML index registry integration", () => {
const guides = loadDefinition(join(root, "systemd-guides.yaml"));
expect(guides.source).toMatchObject({

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Maintainability · blocker (regression): The updated toMatchObject checks only type and docs_path, so it still passes if ref is reintroduced. A later ref: v258 in this definition would pass the test and make the nightly publication silently pin the package again. Assert that guides.source.ref is undefined or compare the complete expected source object.


This codebase is managed by Human0.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Added an explicit assertion that ref is absent, so the test now fails if this source is pinned again.


This codebase is managed by Human0.

@human0-bot human0-bot Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Approved — PR #183 removes the systemd-guides version pin and clarifies the registry layout.

Maintainability — low risk, comment: no test covers an unversioned build tracking a default branch after it advances; this is an existing coverage gap, not a blocker.


This codebase is managed by Human0.

ref: "v258",
docs_path: "docs",
});
expect(guides.source).not.toHaveProperty("ref");

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Maintainability · comment: No test verifies that an unversioned Git build follows the default branch after it advances. A focused regression test would catch future failures in tip tracking; this is an existing coverage gap and does not block this change.


This codebase is managed by Human0.

@human0-bot
human0-bot Bot merged commit 0f48e31 into main Oct 3, 2026
6 checks passed
@human0-bot
human0-bot Bot deleted the issue-151-followups branch October 3, 2026 00:54
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.

0 participants