[Eduardo Villalpando Mello (edvilme)]

This pull request automates the npm package release workflow for the api package by updating the Azure pipeline configuration. Now, merging a stable version change in api/package.json to main will automatically trigger the pipeline to build, test, and publish the package, reducing manual intervention and risk of error. Manual preview releases remain possible, and other changes will still validate the package without publishing.

Pipeline automation and release process:

• The pipeline is now triggered automatically on changes to api/package.json in the main branch, ensuring that stable version bumps initiate the release process.
• A new version check step compares the api/package.json version in the latest commit to its parent; if a stable version bump is detected (i.e., no pre-release tag), the package is published.
• The publish stage condition has been updated to publish either when the publishPackage parameter is set or when a stable version bump is detected, automating the release for stable versions while preserving manual control for preview releases.

Documentation update:

• The CONTRIBUTING.md file now documents the new release automation, clarifying when and how the npm pipeline is triggered and how preview releases are handled.

[Bill Schnurr (bschnurr)]

🔒 Automated review in progress — Bill Schnurr (@bschnurr) is auto-reviewing this PR.

[Copilot]

🟢 Approval recommended

No active review issues remain for the automated stable-release changes.

No open issues 🎉

What changed in this PR

Automates stable releases of the public API npm package when api/package.json changes on main, while preserving the existing build, test, and approval process.

Changes:

• Triggers the npm pipeline for API manifest changes on main.
• Enables publishing when the version differs from the parent commit and has no prerelease tag, while retaining explicit manual publishing.
• Documents automatic stable releases, build-only runs, and manual preview releases.

File	Description
CONTRIBUTING.md	Documents release automation and manual preview publishing.
build/​azure-pipeline.npm.yml	Adds the manifest trigger, version comparison, and automatic publish condition.

_{Review effort: Balanced}

[Bill Schnurr (bschnurr)]

Result: 🔴 could-not-verify

Verification details

Verification: Automated verification is best effort. The PR author remains responsible for testing.

Summary: [unavailable] Container verification could not start and local execution was not authorized for this PR HEAD: C:\Program Files\RedHat\Podman\podman.EXE --connection pyrx-automation failed: stderr: Error: unable to start container "058d1e54b6f5da538b23ffc020b592628678de9cd893ae7257724df67547a5fd": crun: open `memory.max` for writing: No such file or directory: OCI runtime attempted to invoke a command that was not found

Test runs: none recorded.

[Bill Schnurr (bschnurr)]

Approved via Review Center.

[Rich Chiodo (rchiodo)]

Approved via Review Center.