search

koopjs / koop-provider-marklogic

A Koop Provider that can be used to exposed data in MarkLogic via Esri feature services
https://koopjs.github.io/koop-provider-marklogic/
Other
6 stars 11 forks source link

Update koop-provider-marklogic on npm #165

Closed jkerr5 closed 1 year ago

jkerr5 commented 4 years ago

@rgwozdz we need to push the latest provider to npm. Do you have a process for that in koop?

rgwozdz commented 4 years ago

Do you want to publish it under the koopjs NPM org?

rgwozdz commented 4 years ago

For most of the koopjs repos, the process is:

  1. commit that includes appropriate version bump and Changelog entry. Commit message should be :package: <version>. Replace <version> with the new package version.
  2. Do a github release; we use gh-release to automate.
  3. Publish to NPM
jkerr5 commented 4 years ago

Yes, we would like to update to package here https://www.npmjs.com/package/@koopjs/provider-marklogic. @dmfenton did the first and only publish of it 2 years ago so we need to get it updated with the current version (1.1.0)

rgwozdz commented 4 years ago

Ok, will do. Standby.

rgwozdz commented 4 years ago

@jkerr5 - master is still at package version 1.0.0 . It won't be publishable until you bump the version because it will conflict with what is already on NPM. Bump the package version to 1.1.0 and let me know - then I will publish.

rgwozdz commented 4 years ago

@jkerr5 I see you bumped the version, thanks.

Sorry, I didn't notice before that the package name is currently koop-provider-marklogic, which is different then then published NPM name @koopjs/provider-marklogic. Not sure how that happened. We should change the package name to @koopjs/provider-marklogic for consistency and so that we can publish to the same NPM module. Happy to do that for you if you like.

jkerr5 commented 4 years ago

Oh yeah, I didn't notice that either! I'll update it and then I need to fix the tag on our release too so it get the right commit. I'll update when I have that fixed.

jkerr5 commented 4 years ago

OK, I updated the v1.1.0 tag to the correct commit so hopefully everything is correct now.

rgwozdz commented 4 years ago

Having an issue publishing - the package is so large (73 Mb) that our rotating one-time-password (for MFA) changes during the publish, and thus the publish get rejected. Any way to slim down the repo? Can certain things be left out of the NPM with .npmignore?

rgwozdz commented 4 years ago

@jkerr5 - it is the gradle-4.3.1-bin.zip file - very big. Does that need to be pushed to NPM?

jkerr5 commented 4 years ago

No, that doesn't need to be in the repo. Sorry about that! I'll fix and update the release again :/

jkerr5 commented 4 years ago

OK, I removed that zip file so it should be better now.

rgwozdz commented 4 years ago

Boom! It's published.

jkerr5 commented 4 years ago

Thanks!

jkerr5 commented 3 years ago

Hey @rgwozdz, we have 1.2.0 available now so we need to push this to npm again. Is there a way we can do that or automate it so we don't have to bug you for each release?

jkerr5 commented 3 years ago

@rgwozdz any thoughts on this?

jkerr5 commented 1 year ago

Closing this as we will request via a new ticket for the next release.