Skip to content
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

chore: force v1.0.1 #20

Merged
merged 1 commit into from
Nov 2, 2023
Merged

chore: force v1.0.1 #20

merged 1 commit into from
Nov 2, 2023

Conversation

inigomarquinez
Copy link
Member

Description

As v1.0.0 was published by mistake on npm, we need to force the version to v1.0.1

Related Issue

No issue related

Motivation and Context

Create GH release and publish to npm

How Has This Been Tested?

No testing needed

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Other

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

As v1.0.0 was published by mistake on npm, we need to force the version to v1.0.1
@inigomarquinez inigomarquinez merged commit a46f6bb into main Nov 2, 2023
7 checks passed
@inigomarquinez inigomarquinez deleted the inigomarquinez-patch-1 branch November 2, 2023 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

None yet

2 participants