Skip to content

chore: repoint links and package metadata to machine-made - #1

Open
ricardofrantz wants to merge 1 commit into
mainfrom
ns/repoint-machine-made
Open

ricardofrantz wants to merge 1 commit into
mainfrom
ns/repoint-machine-made

Conversation

@ricardofrantz

@ricardofrantz ricardofrantz commented Oct 26, 2026 •

Copy link
Copy Markdown
Collaborator

Why

The repository moved to machine-made/vscode-diff-next. GitHub redirects git and web URLs, but package metadata and docs still name the old owner. This PR points them at the new owner. It also removes a local Windows user path from a script usage example.

Scope

File Change
package.json repository.url, bugs.url and homepage use machine-made/vscode-diff-next.
README.md CI badge, GitHub badge, Releases link, the link to the sibling extension and the repository row of the sibling table use the new owner.
SECURITY.md The private vulnerability report link uses the new owner.
docs/RELEASING.md The link to the sibling release guide and the two gh secret set ... -R commands (VSCE_PAT, OVSX_PAT) name the new owner.
update-extension.ps1 The -Workspace usage example now reads C:\path\to\vscode-diff-next.
LICENSE, NOTICE The author name now reads "Ricardo Frantz".

The package has no qna field. The Marketplace builds that link from repository, so no new field is needed.

The CI and release workflows use github.repository, so they follow the move without a change.

Kept on purpose

  • publisher: RicardoFrantz and the Marketplace item id RicardoFrantz.diff-next. These are registry identities, not GitHub owners. A change would create a new extension and orphan current installs.
  • The RicardoFrantz.pdf-preview-next id in the README and NOTICE, and the publisher text in the README.
  • The RicardoFrantz.diff-next strings in update-extension.ps1, update-extension.sh, .github/workflows/release.yml and the CHANGELOG.md entry for the first release.
  • The sample paths in scripts/smoke-paths.js (C:\Users\Test\repo, /home/u/proj). They are test inputs, not real home paths.
  • Git history.

Verification

Check How it ran Result
Install npm ci (Node 22, npm 10) Fails on the committed lockfile: 16 resolved entries (8 packages, listed twice) point to registry.npmmirror.com, which returns 403 here. With those entries temporarily switched to registry.npmjs.org (not committed), it passes: 390 packages, 18 s. The integrity hashes are unchanged.
Lint npm run lint Pass, 8 s
Compile npm run compile Pass, 6 s
Smoke npm run smoke (5 scripts) All five pass, 2 s
Package contents npx @vscode/vsce ls Exit 0, 54 files
Package npx @vscode/vsce package (output outside the repo) Exit 0, 56 files, 950.56 KB
Audit npm audit --omit=dev --audit-level=high Exit 1: 2 critical findings in simple-git 3.36.0 and @simple-git/argv-parser (advisory GHSA-v5rq-49vh-5v5c). Not related to this PR. The CI audit step will report the same.

A search for ricardofrantz (case-insensitive) across the tree now finds only the kept items above.

I did not touch the lockfile or the dependencies. Both findings above (mirror URLs in package-lock.json, the simple-git advisory) deserve their own change.

After merge

  1. Publish a patch release to the VS Code Marketplace. The listing shows the new Repository, Issues and Homepage links only after a new version is published.
  2. Keep publisher RicardoFrantz. Check that the VSCE_PAT secret and the marketplace-publish environment (with its reviewers) exist on machine-made/vscode-diff-next before the release run. OVSX_PAT is optional: the extension is not on Open VSX.
  3. The repository has the Issues tab switched off today. The bugs link on the Marketplace listing points at /issues, so switch Issues on in the repository settings or the link leads to a 404.

https://claude.ai/code/session_016vMfdfTLtvm4G2UANfJw8q


Generated by Claude Code

The repository now lives at github.com/machine-made/vscode-diff-next.
Point package.json repository, bugs and homepage at the new owner.
Point the README, SECURITY.md and docs/RELEASING.md links and commands at the new owner.
Replace the local Windows user path in the update-extension.ps1 usage example with a placeholder.
Keep the Marketplace publisher id and the extension ids as they are.
Use the short author name in the LICENSE and NOTICE files.

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

Copy link
Copy Markdown
Collaborator Author

@cubic-dev-ai review


Generated by Claude Code

Copy link
Copy Markdown
Collaborator Author

@coderabbitai review


Generated by Claude Code

@cubic-dev-ai

cubic-dev-ai Bot commented Oct 26, 2026

Copy link
Copy Markdown

@cubic-dev-ai review


Generated by Claude Code

@ricardofrantz I have started the AI code review. It will take a few minutes to complete.

@coderabbitai

coderabbitai Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review.

Recent review info
Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Central YAML; Path: .coderabbit.yaml
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: bab1ec0f-ba9f-4e3e-b24c-102c74ba794f
Commits

Reviewing files that changed from the base of the PR and between befe050 and ee02a9a.

Files selected for processing: 7
  • LICENSE
  • NOTICE
  • README.md
  • SECURITY.md
  • docs/RELEASING.md
  • package.json
  • update-extension.ps1

Limit details: You’ve used all 10 included reviews currently available.

Walkthrough

Repository links and metadata now use the machine-made organization. The copyright and publisher attributions omit the middle initials, and the workspace example uses a generic path.

Changes: Repository identity updates

Layer / File(s) Summary
Repository references and attribution
README.md, package.json, SECURITY.md, docs/RELEASING.md, LICENSE, NOTICE, update-extension.ps1
Repository links and metadata now use the machine-made organization. The attribution text omits the middle initials, and the workspace example uses C:\path\to\vscode-diff-next.

Priority: Low

Estimated code review effort: 2 (Simple) | ~5 minutes

Change: Other

Merge Risk: Minimal · up to ee02a

No actionable merge-blocking risk remains from the reviewed changes.

Architecture risk: Low · up to ee02a

The change affects 7 systems.

Changed systems: docs, LICENSE, NOTICE, package.json, README.md, SECURITY.md, update-extension.ps1

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

  • observed — docs (service) was modified; 1 changed file maps to changed impact.
  • observed — LICENSE (service) was modified; 1 changed file maps to changed impact.
  • observed — NOTICE (service) was modified; 1 changed file maps to changed impact.
  • observed — package.json (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

  • observed — Modified behavior in LICENSE: The 2026 copyright attribution changes from Ricardo A. S. Frantz to Ricardo Frantz.
  • observed — Modified behavior in NOTICE: The publisher attribution removes the middle initials “A. S.”
  • observed — Modified behavior in README.md: The CI and GitHub badges now link to machine-made/vscode-diff-next instead of ricardofrantz/vscode-diff-next; the license badge is unchanged.
  • observed — Modified behavior in README.md: The vscode-pdf Next link now points to machine-made/vscode-pdf-next instead of ricardofrantz/vscode-pdf-next.
Pre-merge checks: Passed 5
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly and concisely describes the main changes: updating repository links and package metadata to the machine-made organization.
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (7 skipped: 7 unsupported.)

Finishing Touches: 💡 1
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
🛠️ Fix failing CI checks: 💡
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Usage-based review receipt

  • Mode: Continue automatically
  • Reviewed files: 7
  • Waived: $1.75 (charged $0.00)
  • View usage details

Note

This review exceeded your plan’s limits and used usage-based reviews—free during trial, billed after paid activation unless disabled. Manage usage-based reviews.

Comment @coderabbitai help to get the list of available commands.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

No issues found across 7 files

View guided diff | Turn on auto-fix | Re-trigger cubic

@coderabbitai

coderabbitai Bot commented Oct 26, 2026 •

Copy link
Copy Markdown
⚠️ Action not completed

Already reviewed the last commit. Use @coderabbitai full review to rerun a review of the entire changeset.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Copy link
Copy Markdown
Collaborator Author

@coderabbitai review


Generated by Claude Code

@coderabbitai

coderabbitai Bot commented Oct 26, 2026 •

Copy link
Copy Markdown
⚠️ Action not completed

Already reviewed the last commit. Use @coderabbitai full review to rerun a review of the entire changeset.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

This branch has not been deployed

No deployments
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