fix(ci): properly fail release job when npm publish fails

[safaiyeh]

Problem

The release job was configured with || true which caused it to always succeed, even when npm publishing failed. This made it confusing to determine the actual status of releases.

Solution

Remove || true from the semantic-release command so that publishing failures are properly reported.

Changes

• .circleci/config.yml: Remove error suppression from release command

[greptile-apps]

Greptile Summary

Removes error suppression (|| true) from the semantic-release command in the CI pipeline, allowing npm publishing failures to be properly reported instead of silently ignored.

• The || true pattern was present since the initial CircleCI setup in 2020
• semantic-release already handles "nothing to release" scenarios gracefully with exit code 0
• The only failures that should occur are legitimate errors (authentication, network issues, etc.) that need visibility

Confidence Score: 5/5

• This PR is safe to merge with no risk
• Single-line fix that corrects a CI configuration issue - removes error suppression that was masking actual publishing failures, no logic changes to code
• No files require special attention

Important Files Changed

Filename	Overview
.circleci/config.yml	Removed `