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

Version 0.3.0 not available at npm #37

Open
brucruz opened this issue Jan 8, 2024 · 8 comments
Open

Version 0.3.0 not available at npm #37

brucruz opened this issue Jan 8, 2024 · 8 comments

Comments

@brucruz
Copy link

brucruz commented Jan 8, 2024

The current version 0.3.0 of kysely-data-api is not available at https://www.npmjs.com/package/kysely-data-api.
image
It seems there was an error in the GH action script that would publish it.
Can you publish it, please?

@jayair
Copy link
Contributor

jayair commented Jan 9, 2024

Oh where did you see 0.3.0 btw?

@brucruz
Copy link
Author

brucruz commented Jan 10, 2024

Here in the master branch: https://github.com/sst/kysely-data-api/blob/master/package.json
image

@jayair
Copy link
Contributor

jayair commented Jan 13, 2024

Oh we might've not cut a release. Let me check on this.

@festusyuma
Copy link

festusyuma commented Mar 30, 2024

Hi @jayair . please is this packaege still being mantained. I see 1.0.0 in the changelog but on npm, the latest version I see is 0.2.1 and don't see any beta versions. how can I install the latest version. thanks

Tried installing using the npm but only got the package.json file and ReadMe.

@woconnor
Copy link
Contributor

woconnor commented Apr 6, 2024

Hello @jayair, I opened PR #40 to fix the build. The build was failing due to TypeScript errors, which was preventing release.

@woconnor
Copy link
Contributor

woconnor commented Apr 9, 2024

I opened another PR #41 to sync pnpm-lock.yaml with package.json. I missed this in the first PR and it caused the release workflow to fail, unfortunately.

@notsoluckycharm
Copy link

Any update on this ? @jayair @woconnor

@woconnor
Copy link
Contributor

Any update on this ? @jayair @woconnor

My fix went in, which caused a release PR #42 to be automatically created, but it needs to be merged in order to release a new version.

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

No branches or pull requests

5 participants