You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello @rgwozdz - based on #165, we're reaching out to you to see if you are still able to publish our koop-provider-marklogic releases to npm. The output of npm pack is now a 12kb zip named koopjs-provider-marklogic-2.0.0.tgz - it's also attached to our 2.0.0 release page - https://github.com/koopjs/koop-provider-marklogic/releases/tag/2.0.0 .
In the comments in #165, you mention updating a changelog. We don't have a CHANGELOG.md file, we're just adding release notes to each release. If such a file is needed though, we're happy to create one.
Please let me know if you're still able to publish our releases to npm and any changes you require by us before doing so. Thanks!
The text was updated successfully, but these errors were encountered:
Hello @rgwozdz - based on #165, we're reaching out to you to see if you are still able to publish our koop-provider-marklogic releases to npm. The output of
npm pack
is now a 12kb zip namedkoopjs-provider-marklogic-2.0.0.tgz
- it's also attached to our 2.0.0 release page - https://github.com/koopjs/koop-provider-marklogic/releases/tag/2.0.0 .In the comments in #165, you mention updating a changelog. We don't have a
CHANGELOG.md
file, we're just adding release notes to each release. If such a file is needed though, we're happy to create one.Please let me know if you're still able to publish our releases to npm and any changes you require by us before doing so. Thanks!
The text was updated successfully, but these errors were encountered: