Skip to content

Fix: ensuring types are loaded in newer typescript versions #50

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 5, 2025

Conversation

stevematney
Copy link
Contributor

Summary of PR changes

  • Ensuring types load correctly downstream.
  • Updating commitlint and semantic-release packages

@stevematney stevematney force-pushed the fix-types-resolution branch from 1f3a798 to 3c0201e Compare March 5, 2025 17:49
Copy link

@JavierHuanca JavierHuanca left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@stevematney stevematney force-pushed the fix-types-resolution branch from 44b42aa to 167121b Compare March 5, 2025 18:11
@im-pipeline-bot
Copy link
Collaborator

This PR is part of this prerelease version for testing: 4.0.5-fix-types-resolution-167121b.1

You can test it by using:

npm install react-html-element@4.0.5-fix-types-resolution-167121b.1

@stevematney
Copy link
Contributor Author

I have confirmed this works with the test release, and will merge using admin permissions with Javier's approval.

@stevematney stevematney merged commit c451149 into main Mar 5, 2025
6 checks passed
@stevematney stevematney deleted the fix-types-resolution branch March 5, 2025 18:39
@im-pipeline-bot
Copy link
Collaborator

🎉 This PR is included in version 4.0.5 🎉

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants