chore: prepare v1.50.0 release

[Esquetta]

Summary

• bump package metadata to 1.50.0
• add v1.50.0 changelog notes
• pin public GitHub Action examples to v1.50.0

Verification

• release metadata tests: 18 passed
• feature suite before release prep: 597 passed
• GitHub PR feat: add corpus quality gates to GitHub Action #16 CI passed

[qodo-code-review]

PR Summary by Qodo

Prepare v1.50.0 release (metadata, changelog, pinned docs)

📝 Documentation ⚙️ Configuration changes 🕐 Less than 10 minutes

AI Description

• Bump npm package metadata from 1.49.0 to 1.50.0 for release publishing.
• Add v1.50.0 changelog entry covering new Action metrics inputs and security hardening.
• Update public GitHub Action usage examples to pin ref/version at v1.50.0.

Diagram

graph TD
  R["Release v1.50.0"] --> PJ["package.json"] --> PL["package-lock.json"]
  R --> CL["CHANGELOG.md"]
  R --> RD["README.md"] --> AC{{"GitHub Action consumers"}}
  R --> GA["docs/github-action.md"] --> AC

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Automate releases with release-please (or Changesets)

• ➕ Reduces manual version/changelog/doc pin drift
• ➕ Creates consistent, repeatable release PRs and tags
• ➕ Can enforce changelog + version bump policy automatically
• ➖ Upfront setup and workflow changes
• ➖ May require adapting current changelog/release conventions
• ➖ Less flexibility for one-off release-note curation

2. Document only the action ref (omit separate `version:` in examples)

• ➕ One fewer value to keep in sync in docs
• ➕ Encourages consumers to rely on the action’s bundled CLI
• ➖ If action and npm package can diverge, consumers lose explicit reproducibility
• ➖ May be incompatible with current action design/expectations

Recommendation: The current approach is appropriate for a manual release-prep PR: it keeps npm metadata, changelog, and published Action examples aligned at v1.50.0. If this kind of PR is frequent, consider adopting release automation (release-please/Changesets) to prevent doc pinning and changelog/version bumps from drifting over time.

Files changed (5) +41 / -27

Documentation (3) +38 / -24

CHANGELOG.mdAdd v1.50.0 changelog entry +14/-0

Add v1.50.0 changelog entry

• Adds release notes for 1.50.0 dated 2026-07-21. Highlights new GitHub Action inputs/outputs around corpus metrics and regression gates, plus security-oriented handling of paths and report contents.

CHANGELOG.md

README.mdPin README GitHub Action example to v1.50.0 +2/-2

Pin README GitHub Action example to v1.50.0

• Updates the example workflow to use Esquetta/CodexPluginDoctor@v1.50.0 and sets the 'version' input to 1.50.0 for reproducible usage.

README.md

github-action.mdUpdate GitHub Action guide examples to v1.50.0 +22/-22

Update GitHub Action guide examples to v1.50.0

• Replaces v1.49.0 references with v1.50.0 across multiple example snippets. Keeps the action ref and 'version' input aligned throughout the guide.

docs/guides/github-action.md

Other (2) +3 / -3

package-lock.jsonBump lockfile package version to 1.50.0 +2/-2

Bump lockfile package version to 1.50.0

• Updates the root package version fields from 1.49.0 to 1.50.0 to match the release version.

package-lock.json

package.jsonBump npm package version to 1.50.0 +1/-1

Bump npm package version to 1.50.0

• Updates the package version from 1.49.0 to 1.50.0 as part of release preparation.

package.json

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review