Skip to content

fix: fixing semantic release failure#162

Closed
sridhargk wants to merge 1 commit intomasterfrom
sridhargk-patch-1
Closed

fix: fixing semantic release failure#162
sridhargk wants to merge 1 commit intomasterfrom
sridhargk-patch-1

Conversation

@sridhargk
Copy link
Copy Markdown
Collaborator

Update .travis.yml to run successful semantic release

PR summary

Fixes: <! -- link to issue -->

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

Update .travis.yml to run successful semantic release
@sridhargk sridhargk requested a review from jkalandaibm November 7, 2025 13:49
@sridhargk sridhargk self-assigned this Nov 7, 2025
@sridhargk sridhargk closed this Nov 7, 2025
@sridhargk sridhargk deleted the sridhargk-patch-1 branch November 7, 2025 13:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant