Skip to content

fix: resolve readme page render on the npm package page - #365

Merged
sridhargk merged 3 commits into
masterfrom
fix-package-render
Oct 20, 2026
Merged

sridhargk merged 3 commits into
masterfrom
fix-package-render

Conversation

@sridhargk

Copy link
Copy Markdown
Collaborator

PR summary

Fixes:

  • resolve readme page render on the npm package page
  • pass package version on slack notification
  • update readme to new node versions

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>
Signed-off-by: Sridhar G K <gksridhar09@gmail.com>
Signed-off-by: Sridhar G K <gksridhar09@gmail.com>
@sridhargk sridhargk self-assigned this Oct 20, 2026
@sridhargk
sridhargk merged commit 8209a88 into master Oct 20, 2026
6 checks passed
@sridhargk
sridhargk deleted the fix-package-render branch October 20, 2026 06:21
@DevxNetworkServices

Copy link
Copy Markdown
Member

🎉 This PR is included in version 0.42.1 🎉

The release is available on:

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.

2 participants