docs(release): 🚀 automate npm publishing via GitHub Actions

[htnabe]

Summary

Automate npm publishing and GitHub Release creation after a version bump reaches main.

Changes

• Add a guarded GitHub Actions workflow for npm trusted publishing and release tags.
• Run lint, fixture tests, runtime smoke checks, and package dry-run checks before publishing.
• Align release documentation and AGENTS.md with the automated workflow.

Validation

• npm test (105 tests passed)
• npm run test:runtime
• npm run lint
• npm run build
• npm pack --dry-run
• Prettier check

Risks

• npm trusted publishing must be configured for this repository, workflow filename, and the publish GitHub environment before the first automated release.
• The existing release:plugin script remains only as a legacy local publish helper.

Checklist

• Conventional commit(s) with gitemoji used
• Commit granularity is meaningful
• Tests and lint were run as appropriate
• Documentation updated if needed

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[Copilot]

Pull request overview

Automates npm publishing and GitHub Release creation for prettier-plugin-go-template by introducing a guarded GitHub Actions workflow that runs release validations and then publishes/tags/releases once a version bump lands on main.

Changes:

• Adds a Publish Release workflow to validate, publish to npm (OIDC trusted publishing), tag, and create a GitHub Release.
• Updates publishing documentation to reflect automated release flow and guardrails.
• Updates AGENTS.md to clarify release:plugin is legacy and point to the workflow.

Reviewed changes

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

File	Description
docs/develop/publishing.md	Updates release/publishing instructions to reflect GitHub Actions-based publishing and tagging.
AGENTS.md	Aligns project agent guidance with the new automated publishing workflow and legacy script usage.
.github/workflows/publish.yaml	Introduces the automated publish/tag/release GitHub Actions workflow with validation guardrails.

Suppressed comments (1)

.github/workflows/publish.yaml:101

• Same Node version pinning issue here: node-version: 22 may not satisfy the repo's engines.node constraint (>=22.12.0).

          node-version: 22

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.