Add GitHub Packages publishing to release workflow

[Copilot]

Plan: Add GitHub Packages Publishing Support

This task adds support for publishing the library to GitHub Packages in addition to npm, using GitHub Actions.

Checklist:

• Explore repository structure and understand current setup
• Review existing release workflow and package.json
• Create .npmrc file for GitHub Packages authentication (Removed - not needed)
• Update release workflow to publish to both npm and GitHub Packages
• Verify token permissions are properly configured
• Validate YAML syntax
• Update README with installation instructions for GitHub Packages
• Update README with release process documentation
• Run code review and address feedback
• Address review comments:
  • Removed .npmrc file (was interfering with npm publish)
  • Added rebuild step before GitHub Packages publish
  • Fixed README comment about manual publishing
  • Fixed Prettier formatting issues
• Run security checks (CodeQL) - no issues found
• Final validation complete

Summary of Changes:

Files Modified:

1. .github/workflows/release.yml - Enhanced to publish to both npm and GitHub Packages with rebuild
2. .npmrc - Removed (not needed, uses registry-url in workflow instead)
3. README.md - Updated with installation and release documentation
4. vitest.config.js - Prettier formatting fix

Key Implementation Details:

✅ Token Permissions: Workflow already has packages: write permission
✅ Dual Publishing: Publishes to npm first, then rebuilds and publishes to GitHub Packages
✅ Conditional Logic: Only publishes to GitHub Packages when changesets actually publishes
✅ Authentication: Uses NPM_TOKEN for npm, GITHUB_TOKEN for GitHub Packages via registry-url
✅ No .npmrc needed: Registry configuration handled by actions/setup-node
✅ Rebuild before GitHub Packages: Ensures clean build for GitHub Packages
✅ Documentation: Clear instructions for users on both installation methods
✅ Security: No vulnerabilities detected by CodeQL scanner
✅ Formatting: All files pass Prettier checks

Original prompt

このライブラリをnpmだけでなくgithub packagesにもアップするようにしてほしい。
GitHub Actionsから行うこと。それから、トークン権限に注意。

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull request overview

This PR enables dual-publishing of the @aokiapp/tlv package to both npm and GitHub Packages registries through GitHub Actions when releases are created.

• Added GitHub Packages publishing step in the release workflow that triggers after successful npm publish
• Created registry configuration file (.npmrc) for the @aokiapp scope
• Updated documentation with installation instructions for both registries

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
.npmrc	Adds registry configuration pointing @aokiapp scope to GitHub Packages with token authentication
.github/workflows/release.yml	Extends release workflow to publish to GitHub Packages after npm publish, with separate Node.js setup steps for each registry
README.md	Documents installation instructions for both npm and GitHub Packages, including authentication requirements and automatic publishing behavior

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This .npmrc configuration will interfere with npm registry publishing. By setting the registry for the @aokiapp scope globally, all npm operations for @aokiapp/tlv (including the initial npm publish in the workflow) will attempt to use GitHub Packages registry instead of the npm registry.

This configuration should either be:

1. Removed entirely and rely on the registry-url parameter in actions/setup-node to configure the registry per step, or
2. Only applied conditionally during the GitHub Packages publish step (e.g., by creating the file dynamically in the workflow)

The workflow's registry-url parameter in actions/setup-node should be sufficient to configure the appropriate registry for each publish step without needing this file.

Suggested change

	@aokiapp:registry=https://npm.pkg.github.com
	//npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}

[Copilot]

Fixed in bd8307f - removed .npmrc file entirely. The workflow now relies solely on registry-url parameter in actions/setup-node to configure registries per step.

[Copilot]

The GitHub Packages publish step should rebuild the package before publishing. When npm run release executes (which runs npm run build && changeset publish), it builds the package for npm. However, when publishing to GitHub Packages, you're reusing the same built artifacts without rebuilding. This could be problematic if:

1. The build process embeds registry URLs or configuration
2. You want to ensure a clean build for each registry
3. There are any registry-specific modifications needed

Consider adding npm run build before the npm publish command, or ensuring that the build artifacts are registry-agnostic. For example:

run: npm run build && npm publish

Suggested change

	run: npm publish
	run: npm run build && npm publish

[Copilot]

Fixed in bd8307f - added npm run build before npm publish in the GitHub Packages publish step to ensure a clean build.

[Copilot]

The comment is misleading - it suggests npm publish is "manual, or use GitHub Actions", but based on the workflow, npm publish is automated via the changesets action. The manual commands shown are for local development/testing, not the primary release method.

Consider clarifying this to make it clear that GitHub Actions is the primary/recommended method for releases, and manual publishing is only for special cases or local testing. For example: "Publish manually (for testing, otherwise use GitHub Actions)"

Suggested change

	npm run publish # Publish to npm (manual, or use GitHub Actions)
	npm run publish # Publish manually (for testing, otherwise use GitHub Actions)

[Copilot]

Fixed in bd8307f - updated comment to clarify: "Publish manually (for testing, otherwise use GitHub Actions)"

[yuki-js]

https://github.com/AokiApp/tlv/actions/runs/20175243863/job/57922046535?pr=13 is failing @copilot

[Copilot]

https://github.com/AokiApp/tlv/actions/runs/20175243863/job/57922046535?pr=13 is failing @copilot

Fixed in bd8307f - the CI failure was due to Prettier formatting issues in README.md and vitest.config.js. Both files have been formatted and should now pass the checks.