Skip to content

chore: fix semantic release failure due to npm registry#285

Merged
sridhargk merged 1 commit intomasterfrom
fix-package-release
Feb 12, 2026
Merged

chore: fix semantic release failure due to npm registry#285
sridhargk merged 1 commit intomasterfrom
fix-package-release

Conversation

@sridhargk
Copy link
Collaborator

PR Checklist

Please make sure that your PR fulfills the following requirements:

  • The commit message follows the Angular Commit Message Guidelines.
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • New tests
  • Build/CI related changes
  • Documentation content changes
  • Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Signed-off-by: Sridhar G K <gksridhar09@gmail.com>
@sridhargk sridhargk merged commit bafda6a into master Feb 12, 2026
7 checks passed
@sirijaibm sirijaibm requested review from sirijaibm and removed request for sirijaibm February 12, 2026 04:36
@DevxNetworkServices
Copy link
Collaborator

🎉 This PR is included in version 0.51.16 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants